When a buyer navigates between a brand’s storefront and checkout domains, it’s essential to preserve tracking data for accurate attribution. LoudCrowd uses a tracking ID stored in the browser’s local storage under the key lc_anon_user_id.
Problem
If the storefront and checkout pages are hosted on different domains, the tracking ID may be lost during the redirect to the checkout domain. This causes issues with linking a buyer’s order back to the original storefront landing event.
For example:
Storefront domain: www.[brandname].com
Checkout domain: shop.[brandname].com
In this scenario, when a buyer moves from the storefront domain to the checkout domain, the tracking ID does not automatically carry over unless additional handling is implemented.
Why This Matters
The tracking ID allows LoudCrowd to:
Generate a unique identifier when a buyer first visits a creator’s storefront.
Attribute conversions (orders) back to the initial storefront landing event.
Without preserving this ID, orders cannot be accurately tied to the originating storefront traffic source.
Required Implementation
To maintain accurate attribution:
Generate Tracking ID on Storefront Load
When a buyer first visits the storefront, LoudCrowd creates a tracking ID and saves it in local storage under the key:
lc_anon_user_id
Preserve Tracking ID Across Domains
When the buyer proceeds to checkout, ensure that the value of lc_anon_user_id is transferred to the checkout domain.
This can be accomplished using one of the following approaches:
Passing the ID through query parameters during the redirect.
Using server-side session handling to bridge the domains (e.g. with cookies).
Confirm Tracking on Checkout Domain
On the checkout page, verify that lc_anon_user_id exists and matches the ID generated on the storefront domain.
By following this process, LoudCrowd will be able to attribute conversion events on the checkout domain back to the original storefront visit.