If you have a Shopify store with Builder’s Shopify App installed, you have access to powerful features, including built-in conversion tracking.
Any time a user clicks from a Builder page to the cart/checkout page and completes a purchase, Builder records a conversion event and writes the order ID to a cookie.
The conversion event also captures a session ID. Conversions are then tied to any Builder content entry that had an impression in that same session.
Because this conversion event is triggered on the front end, the data has to be sent over the wire to be recorded. Thus, conversion events could be slow to post, doubled-counted or dropped altogether. This could happen for any number of reasons, including:
- A user's internet connection is slow or fails before the conversion can be sent
- The user has ad blockers enabled that block the cookie or tracking API completely
- A user closes the window before the API request completes
- Any number of other user- or environment-related reasons
For these reasons, and because a conversion can be tied to multiple content entries, it’s possible that your conversion tracking in Builder can be slightly different from other analytics (such as Shopify’s). For this reason, you should refer to the metrics in your Shopify store for the most meaningful counts. The differences should be immaterial, though, and the directional insights from Builder tracking provide detailed and actionable analysis of how your content entries are performing.
