Web attribution FAQs
Adjust counts the first session as an install for web users. When a user reaches the landing page, it is recorded as a conversion. Additional actions are recorded as events.
Adjust does not use an attribution waterfall for web attribution. We use an Adjust-generated click ID called a reftag for device matching.
No, there is no customizable attribution window for clicks. When a user clicks an Adjust link, they are immediately redirected to the page with the web SDK. Unlike the platform-level app environment, no meaningful gap between click and install occurs.
You can define an inactivity window for reattributions between 0-365 days. This inactivity window is set at the app level, so it applies to all platforms targeted by multi-platform apps.
You can edit the inactivity window at the individual link level. This makes it possible to create link for web use only, which have a different inactivity window than the parent app setting.
Can I redirect users to a site address that doesn’t contain the web base URL set in Adjust’s internal interface?
You can, but Adjust cannot attribute the user. We use the web base URL to determine whether to append the reftag to a destination URL. If the web base URL is not present, we will not append the reftag and no attribution can be made.
Adjust uses Anonymous IP filtering for all web attribution data.
Yes! You can send S2S events to Adjust by including the adid or web_uuid as the device identifier. If you have access to the same browser storage as our web SDK, you can retrieve the web_uuid by querying your backend using javascript. For more information, read about sending S2S events.
We allow GDPR forget and disable measurement using SDK or S2S requests. Using one of these methods, you can notify the Adjust backend if a user no longer wishes to be recorded. For more information, read about our GDPR support here.