Skip to main content

Meta Pixels for Storefronts: Tracking Setup and Events

Updated over 2 weeks ago

Your Zest storefront supports industry-standard tracking pixels so your marketing team can measure ad performance, build retargeting audiences, and track conversion events.

Overview: Supported Tracking Platforms

Zest supports three tracking integrations for Storefronts:

Platform

What You Provide

Meta Pixel

Pixel ID — a numeric string (e.g., 2236089896716902)

Google Tags

Google Tag ID — format G- (GA4), GTM- (Tag Manager), or AW- (Google Ads)

LinkedIn Insights Tag

LinkedIn Partner ID and LinkedIn Conversion ID

All three are optional. Use any combination that fits your marketing stack.

Note: Only install tracking on live production storefronts. Sandbox or staging environments should not receive tracking tags.

Finding Your Meta Pixel Tracking IDs

You only need your Pixel ID — not a full script snippet.

To find your Meta Pixel ID:

  1. Select your ad account or business portfolio.

  2. Click Data Sources in the left sidebar.

  3. Select the pixel you want to connect.

  4. Your Pixel ID appears at the top of the page — it is a string of numbers (e.g., 2236089896716902).

Providing Your IDs to Zest

If the Web Analytics tab is visible in your dashboard:

  1. Go to Settings in your Zest partner portal.

  2. Click the Web Analytics tab.

  3. Enter your IDs in the relevant fields:

    • Meta Pixel ID — your numeric Pixel ID

  4. Click Update.

Changes go live on your storefront immediately after saving.

If you don't see the Web Analytics tab:

Send your tracking IDs to your Zest CSM via email. Include the platform name and the specific ID in the correct format. The Zest team will install them on your storefront.

Verifying Your Tracking Is Working

After saving your IDs (or after Zest confirms installation):

  1. Place a test order on your storefront.

  2. Open your Meta Events Manager and check that events are appearing.

Meta Pixel events Zest sends:

See Meta's documentation for event definitions and specifications.

Event

When It Fires

PageView

On every storefront page load

ViewContent

When a shopper views a product

AddToCart

When a shopper adds a product to their cart

InitiateCheckout

When a shopper proceeds to checkout

AddPaymentInfo

When a shopper enters payment details

Purchase

When an order is completed (includes value and currency)

Important: Use event-based conversion tracking. The storefront order confirmation page shares a URL with the order dashboard view, so URL-based conversion triggers will not work reliably. Use the Purchase event for conversion tracking instead.

Troubleshooting tips

  • If events aren't showing up, verify your DNS records are complete and that cross-domain tracking is enabled in your Meta account settings.

  • Most configuration issues originate from account settings on the brand side rather than the Zest installation itself.

  • Your Zest CSM can provide a verification email template to send to your analytics team if needed.

Updating or Removing Tracking Pixels

If you have the Web Analytics dashboard:

  1. Go to Settings > Web Analytics.

  2. Update or clear the relevant ID field.

  3. Click Save.

If your pixels were installed by Zest engineering:

Email your Zest CSM with updated tag information. Zest can remove or replace existing pixels.

Using separate pixels for different storefronts:

You can apply different tracking configurations to each of your storefronts. For example:

  • A public storefront running paid campaigns can have full pixel tracking enabled.

  • A private employee gifting storefront can have advertising pixels omitted — preventing corporate bulk orders from skewing your D2C ad targeting and optimization.

Cookie Consent and Third-Party Scripts

Cookie consent and the Zest banner

Zest displays a cookie consent notice on storefronts. This banner appears once per customer per browser or device.

  • If your brand manages its own cookie consent, you can suppress the Zest banner from Settings > Web Analytics by turning off Show Cookie Banner.

  • Brand tracking scripts run independently. If you want your scripts to fire only after a customer accepts your own cookie notice, configure that behavior within your tag manager or pixel settings.

Note: Zest's own internal analytics do not collect personal data and run separately from brand tracking pixels.

Retargeting and visitor data

Tracking pixels allow you to retarget anonymous visitors who browse your storefront without capturing personally identifiable information like email addresses. If your goal is email lead capture, route paid traffic through your own website first to collect emails, then redirect to your storefront.

Custom and third-party scripts

Zest can add third-party widget scripts (chat widgets, A/B testing tools, etc.) on a case-by-case basis following engineering review. Contact your Zest CSM to request this. Keep in mind:

  • Zest will implement the embed code and update Content Security Policy settings so the widget can load.

  • You may need to configure the third-party tool to recognize your storefront domain.

  • Custom scripts are outside Zest's support scope — if a script causes unexpected behavior (such as popup conflicts), Zest cannot troubleshoot the third-party tool itself.

Did this answer your question?