Routes

A route pairs one compliant page with one destination and one Meta pixel. It is the piece that turns a clean landing page into tracked, redirected ad traffic. Each route gets its own gate script URL, so you can run several routes on one store and send different campaigns to different pixels.

This page covers managing routes you already have. For setting up your first one, see Create a route.

Read the routes list

Each row in the list shows one route. From left to right you see:

• Label and its status badges. Active or Inactive tells you whether the route is live. OneHop or ZeroHop shows the route's strategy (see below). Default marks the route that catches traffic when no specific route matches. Not configured means the route is missing a piece and will not fire yet.
• The path it serves: the compliant page domain, an arrow, then the destination URL.
• Pixel, the Meta pixel that fires for this route; Key, the route's unique ingestion key; and Code, its short ad-parameter code. Use the copy control on either to grab it.

If a route uses same-origin delivery, you also see a Same-origin badge with the last time it verified, or a Same-origin error badge if the last check failed.

OneHop and ZeroHop

Every route uses one of two strategies for getting a shopper from an ad to your store:

• OneHop: the shopper passes through your compliant page on the way to your store. This is the default and works for most ad setups.
• ZeroHop: the ad points straight at your store, with no compliant page in between. The route's short code has to be pasted into the ad, because nothing else tells Zappush which route the traffic belongs to.

Open a route's detail page to see its code and the exact field to paste it into in Meta Ads Manager, under Ad parameter.

Manage a route

1. Find the route in the list and click Manage.
2. The detail page opens with a configuration panel at the top. Edit any of:
   • Label: the name you recognize the route by.
   • Destination URL: where gated shoppers land on your store.
   • Compliant page: which clean page this route serves.
   • Meta integration: which pixel fires for this traffic.
3. Use the toggle in the top right of the panel to set the route Active or Inactive.
4. When you change anything, a Save changes button appears. Click it to save.

Destination domains and link tracking

Every route can declare the domains a shopper might end up on after passing through your compliant page. When a shopper clicks any link on the compliant page that leads to one of these domains, or a subdomain of one, your Zappush tracking follows them there automatically, so the marketing that brought them keeps credit.

On a route's detail page:

• Destination domains: add each domain your compliant page's traffic might land on. Most routes only need their main destination, but add more if a campaign can land on several of your domains.
• Keep links tracked: on by default. Turn this off for a route that deliberately sends shoppers through more than one hop before reaching your store, so tracking data doesn't carry across a hop you don't want it to.

Below the destination domains, Zappush shows any domain your compliant page's traffic has recently reached that isn't declared yet, so you can add a domain you recognize with one click.

Same-origin

The Same-origin panel is for advanced setups where the gate snippet is served from your store's own host through a reverse proxy, instead of from Zappush. Turn on the Same-origin enabled switch and set a Path prefix (for example /gate) if your setup needs one. Below the switch, Zappush shows whether the path has been verified, when it last verified, or the error from the last failed check. Leave this off unless you have set up the proxy.

Custom scripts

If you are an admin, the detail page has two optional script panels:

• Store page custom script: JavaScript that runs after the tracker on the destination page. Not available on Shopify stores.
• Gate page custom script: JavaScript that runs after the gate script on the compliant page.

Each runs in its own isolated block, so a script error will not break the page. Leave these empty unless you have a specific reason to add code.

This custom script can be injected from the Zappush side itself, so there is no need to add code on your store.

Install snippets

The Install panel shows two snippets, one for each side of the route. For step-by-step instructions on adding the tracker to your platform, see Install the tracker.

Destination page (tracker): add this to the <head> of the site your traffic lands on. It records page views, events, and shopper identity on the destination.

<script async src="https://api.zappush.com/s/<route-key>.js"></script>

Compliant page (gate): add this to the <head> of your compliant page. It captures identity and Meta signals before the redirect and carries them through to the destination. This panel is hidden when same-origin hosting is enabled, because Zappush then serves the gate script automatically from your own domain and no manual install is needed.

<script defer src="https://api.zappush.com/g/<route-key>.js"></script>

Copy the exact snippets from the panel; the key in each URL is unique to the route. See Scripts for a full explanation of what each script does.

You'll know it worked when

The route shows Active in the list, the path reads from your compliant page to your destination, and loading the compliant page redirects shoppers to the destination URL while conversions fire to the pixel you chose.

Next: Compliant pages to edit the page a route points to.