Destinations

A destination is a platform Zappush sends your conversions to: Meta and Google Ads. Open Connections → Destinations to see your destinations and their status. TikTok appears as coming soon. On the Google Ads page you choose which of your events improve which of your conversions.

Meta

Connections → Destinations → Meta is the home for everything about sending data to Meta: your pixels, plus store-wide settings that apply to all of them.

Your pixels

The pixels list shows every Meta pixel connected to this store, each with a status: Connected, Pending, Error, or Not connected. Add a pixel here, or open one to manage it. To connect your first pixel, follow Connect Meta.

A new pixel starts sending your events to Meta as soon as its first connection test passes, so there is nothing to switch on. Sending off means a pixel is connected but not sending anything to Meta; on the Destinations page, the Meta card shows it when every connected pixel is off. A pixel you switch off stays off, even after a later test passes or new credentials are verified for it: Zappush asks whether to turn sending back on when you open the pixel, and changes nothing unless you say yes.

On an Unrestrict store, a pixel receives events only through a route. When no route uses a pixel, a banner above your pixels, on that pixel's page and on the Routes page says it isn't sending to Meta yet. Add it as an additional pixel on an existing route, or create a new route for it. The banner goes away once a route uses the pixel.

A pixel's detail page

Open any pixel to manage it. The page has a tab for each part, and each tab has its own address, so you can bookmark or share it and the browser's Back button moves between them:

• Overview: the pixel's status, the Forwarding switch that turns sending on or off, and its Pixel ID.
• Events: what reaches this pixel.
  • Forwarding chooses which events Zappush sends to this pixel. Core conversion events are always on; you control the rest. If your store generates an event that is not reaching this pixel, the list shows it, ranked by how often it happens, with a one-click way to turn it on. Turning one on only affects events from that point forward; it does not resend anything already skipped. On stores outside Shopify, turning on one of your own custom events first asks you to review its fields. Each field shows the last value your store sent, and you choose to send it, hash it, or leave it out, including fields inside grouped data. You can also hide a field's name. Hash or leave out anything that names a condition, a treatment or a patient, so Meta only learns what you decide. Contact details are never sent this way.
  • Aliases holds your event mappings: send an event to Meta under a different name, only when it matches conditions you set. See Event mappings below, and the standard events for the names Zappush uses.
• Diagnostics: run a connection test, set a test event code, and watch recent activity for this pixel, so you can confirm conversions are arriving. This is also where you verify delivery.
• Offline conversions (plans that include them): set up and record sales that happen away from your website. See Offline conversions.
• Settings: the label, Pixel ID and access token, Replace pixel via Facebook to move this integration to another pixel, and Delete pixel. On Shopify stores it also holds the Draft orders switch, which sends sales you complete from a draft order, such as phone orders, invoices and manual re-orders, to this pixel as purchases. It is off until you turn it on, and drafts completed while it was off are not sent later. Free drafts, such as replacements or gifts, are never sent, so they cannot inflate your purchase count. A draft also follows the draft row in the Orders section of your Shopify source (Connections → Sources → Shopify): Meta receives a draft only when that row and this switch are both on. Google Ads has no such switch, so there the draft row alone decides. Subscription renewals and orders at or below your minimum order value follow the same Orders section, on every destination.

Links saved before the tabs existed still work and open the tab that now holds what they pointed to.

Event mappings

An event mapping tells Zappush to send Meta an event under a name you choose whenever a matching event happens. Use one when Meta expects a standard name that differs from the one your store fires. For example, send Meta a Lead event whenever a shopper views your thank-you page.

Mappings live under Aliases on a pixel's Events tab. Each one has:

• A source event: the event it watches for.
• A new name: the name Meta receives.
• Conditions (optional): which of those events count.
• A "send original event" choice: whether Meta still gets the source event too.
• An on and off switch.

Adding a mapping turns on forwarding for its new name automatically. Turning a mapping off or deleting it never turns forwarding off.

A mapping with no conditions applies to every event of its source name. Every mapping you made before conditions existed keeps working exactly as it did.

Conditions

A condition checks one property of the event. Add conditions when a mapping should fire only for the events that matter, such as the thank-you page view or orders above a set amount.

For a query parameter or a custom property, you also enter its name. A custom property's name must match exactly, capital letters included.

Each type has its own operators:

Amounts have decimals, so "at least 100" is more exact than "greater than 99.99", which misses everything in between.

Groups

Conditions sit in groups. Every condition in a group must match. A mapping fires when any one group matches.

For example, a mapping from checkout_completed to HighValueOrder with two groups:

1. Group one: value is at least 100, and currency equals USD.
2. Group two: custom property plan equals premium.

An order fires this mapping if it is at least 100 USD, if it is a premium plan order, or both. An event that matches several groups, or several mappings with the same new name, sends that name to Meta once.

A mapping can have up to 10 groups, each with up to 10 conditions. A value can be up to 500 characters.

How matching works

• Capital letters never matter for text. Summer-Sale matches summer-sale. The one exception is a custom property's name.
• Addresses compare as domain plus path. Zappush ignores https://, a leading www., the query string, anything after #, and one trailing slash. Path equals /thank-you matches https://www.shop.example/Thank-You/?utm_source=x.
• Numbers and true/false read plain forms. 149.00 counts as 149. The words true and false count in any capitalization.
• Several values match if any one does. That covers ?a=1&a=2 and a list of product IDs. "Does not equal" matches only when none of them equal the value.
• A missing property never matches. That includes "does not equal". Path does not equal /cart does not match an event recorded without a page.

For privacy, conditions cannot test personal details. Zappush refuses a property name such as email or phone, and a value that looks like an email address or phone number, when you save.

Zappush checks conditions once, when the event arrives. Editing or deleting a mapping later does not change events it already received.

Send original event

By default a matching event reaches Meta twice: once under its own name and once under the new name. Switch the "send original event" choice off to send only the new name for matching events. Events that do not match your conditions still send under their own name.

Turning the original off changes only what goes to Meta:

• The original event is still saved with its real values. It still counts in your analytics, revenue, funnels, and shopper timelines.
• Only the send to Meta is skipped. Your delivery reporting shows it as skipped because a mapping replaced it.
• A pixel that runs in the shopper's browser is separate. It still reports its own events, including the ones your compliant pages report themselves.

Zappush holds the original back only when the replacement can go out. If the new name is switched off in Forwarding, or Zappush cannot create the renamed event, the original is sent as usual. When two mappings match one event and either has the original turned off, the original is held back, as long as that mapping's new name is on in Forwarding.

Purchases

Use value, currency, or custom property conditions on purchase mappings.

A purchase can reach Zappush two ways: from the shopper's browser, and from your store's own order confirmation. Only the browser version knows the page address. A condition on page URL, path, query parameter, or referrer misses the other version, so that version can still reach Meta as a Purchase even with the original turned off. Value, currency, and custom property conditions match both versions.

Choosing the new name

The new name can be a standard Meta name such as Lead, or a custom name of your own. Zappush refuses two kinds when you save:

• Purchase, in any capitalization. A Purchase built from another event would reach Meta without the order details it needs to count the sale once.
• Names Zappush reserves for its own events.

Where mappings work

• Unrestrict and Standard. Mappings work the same on both. Conditions, the send original event choice, and every rule above behave identically.
• Same rules as the original. A renamed event follows every rule the original follows: the same consent checks, the same protection of customer details, and the same cleaning and enrichment that raise match quality.
• The main pixel. A mapping runs on the main pixel, the one that sends your events. Additional pixels receive the main pixel's renamed events and lose the originals it holds back. A mapping on a pixel that is only an additional pixel does nothing, so set it on the main pixel. See Send conversions to more than one pixel.

Mappings do not cover everything:

• Sales recorded in your physical store and deals marked won in a CRM never produce a renamed event. They reach Meta under their own names.
• Lead stages have their own setting for the Meta event name, so they are not available as a source event.
• A renamed event never triggers another mapping.

Offers accepted after checkout (Shopify)

When a shopper accepts an offer from an upsell app right after checking out, the order grows after its Purchase already reached Meta. Zappush sends the amount the offer added as a second Purchase, so the whole sale counts. Each accepted offer is sent once, for only what it added, and two offers on one order are two Purchases. Meta counts each one as a separate conversion for the order.

Nothing is sent for changes your staff make to an order in Shopify, for changes that add nothing, for orders that were cancelled, or for orders older than 7 days. This is on by default for every Shopify store.

Store-wide settings

Below the pixels list, Store-wide settings apply to every pixel on the store:

• Event quality: keeps the data you send clean and well matched, so Meta can attribute more of your conversions. See Event Match Quality for what drives match quality and how to raise it.
• Compliance: words that should never be sent to Meta, across every pixel. Covered below.

Ad accounts

Selecting an ad account is what will put spend, return on ad spend, and cost per purchase or lead next to your sales and leads elsewhere in the dashboard, once that ships (see Overview and Leads). It is separate from sending conversions: you can send conversions without selecting an ad account.

1. Open the Events screen and scroll to Delivery health, where your Meta connection already lives.
2. Pick which of your ad accounts should count. You can select more than one, and an account you have not selected is never synced.
3. Deselect an account at any time. Its past numbers stay exactly as they are; only future syncing stops.

Spend will be reported in the ad account's own currency and on its own calendar day, the same way Meta itself reports it, so a spend figure's currency code and day may not line up with your store's own clock.

Compliance: keep terms out of your data

Compliance lets you list words that should never reach Meta. When an event's content matches one, Zappush filters that event out before it leaves for Meta. This is how you keep sensitive product names, condition words, or anything else off the data stream your ads depend on.

Why it matters

Meta's review systems are strict about certain words, especially for Health and Wellness brands. A product name or condition that reads fine to a shopper can be enough for Meta to restrict an account if it shows up in the data tied to your ads. Compliance keeps those words out of the stream entirely, without changing your store, your product names, or how shoppers see your site. The filter runs the moment Zappush is about to send an event onward, and applies to every pixel and every event going forward. It does not rewrite or delete events that were already sent.

Matching is case-insensitive and works on whole words, so blocking cbd filters CBD and Cbd but not cbdoil.

Add or remove a term

1. Type the word you want to block and press Enter or click Add. It appears as a tag in the list.
2. To remove a term, click the remove control on its tag.
3. Click Save changes to apply. Until you save, an Unsaved changes marker shows your edits are not yet live; Discard throws them away.

You'll know it worked when

A new pixel shows as Active in the pixels list, its Diagnostics tab shows events arriving, and any compliance terms you saved stop matching events from flowing to Meta from that point on.

A mapping works when a matching event reaches Meta under the new name and, with the original turned off, the original no longer does. Trigger a matching event on your store, then verify delivery as you would for any event.