Shopify Goal Not Recording Conversions

Symptom: You've set up a goal for a Shopify event add to cart, begin checkout, purchase ... and it shows zero conversions, even though you can see the event happening on your store.

Work through these checks in order. The first two account for the majority of cases.

Step 1: Check whether the pixel is firing at all

In your Shopify admin, go to Settings → Customer events. Find your FigPii pixel in the list and look at the Data column.

The column shows "—" → the pixel is not firing. Continue to step 2.
The column shows data → the pixel is firing correctly and the problem is with your goal configuration. Skip to step 3.

This single check tells you which half of the setup to investigate, and saves you looking in the wrong place.

Step 2: Confirm you replaced the access key placeholder

This is the most common cause of a pixel that never fires.

The pixel code in our setup guide contains a placeholder:

<code>piiTester.src = "https://tracking-cdn.figpii.com/REPLACE_WITH_ACCESS_KEY.js";

If REPLACE_WITH_ACCESS_KEY was not replaced with your own access key, the request returns a 403 error, the FigPii script never loads, and the event is never sent. No error message appears anywhere — in Shopify, in FigPii, or to the visitor. The only visible symptom is the "—" in Shopify's Data column.

To fix it:

Find your access key. It's the number in your FigPii tracking code URL. In https://tracking-cdn.figpii.com/1888276374.js, the access key is 1888276374.
In Shopify, go to Settings → Customer events and open the affected pixel.
Replace every instance of REPLACE_WITH_ACCESS_KEY with your access key. Some pixels contain it more than once.
Save, then click Connect.
Trigger the event on your store and re-check the Data column.

Step 3: Confirm your goal value matches the event value exactly

If the pixel is firing but the goal shows nothing, the goal is listening for a different event name than the pixel is sending.

In FigPii, open Site Goals and compare your goal's event value against the value in the pixel code, character by character. These must match exactly — they are case-sensitive, and a trailing space will break the match.

The event values used by each pixel are listed in Tracking Ecommerce Events on Shopify.

A common cause of mismatch: FigPii offers two methods of tracking Shopify orders, and they use different event names. Custom pixels send purchase. Server-side tracking sends shopify_purchase. If you set up goals following one guide and pixels following the other, they will never match. See Which tracking method should I use? below.

Step 4: Confirm the goal exists at all

Adding the pixel to Shopify is only half the setup. You must also create a matching goal in FigPii, under Site Goals → Add New Definition → New Goal, with the trigger rule set to Custom Event and the event value pasted into the pattern field.

If this step was skipped, the pixel will fire correctly and Shopify will show data, but FigPii has nothing configured to record it against.

Step 5: Check consent settings

If your domain has consent gating enabled, FigPii does not collect data until the visitor accepts. Visitors who decline, or who leave before interacting with the banner, will not register conversions. See Data Collection Blocked By Consent Settings.

Still not working?

Contact us at support@figpii.com with your domain, the goal name, and the pixel name. It helps if you can tell us what the Data column in Shopify shows for that pixel.