Track push ads by network and zone
Separate results by network and zone. Push advertising has no universal macro, cost import or conversion endpoint: each network needs its own verified setup.
Use network and zone as analysis units
The same push advertisement can perform differently across placements. Decide where to store the network, campaign identifier and zone before launch. Create the source connection, flow and offer, and document the labels. Do not merge identical zone numbers from different networks without the source dimension: these identifiers need not be globally unique. Keep standard push and other formats distinguishable when comparing results. Review the network requirements for advertisements, notifications, destination pages and data processing. Technical traffic filtering supports measurement, but it does not establish the quality of every placement or replace compliance with advertising requirements.
Choose macros for the actual network
Cost link templates use utm_campaign={campaignid}&utm_content={zoneid} for PropellerAds, utm_campaign={campaign_id}&utm_content={site_id} for Kadam and utm_campaign={camp}&utm_content={site} for Push.house. These values populate campaign and ad group fields. You can additionally retain the zone in a documented sub field for analysis. Similar macro names do not imply compatibility between networks. Treat the generic push preset as a starting point and verify it against the selected account. Follow a real test advertisement and inspect expanded values, campaign matching and zone preservation through the landing page. A missing label initially points to link configuration rather than traffic quality.
Keep two click identifiers separate
inotrack generates the internal clickid. Pass {clickid} in the offer parameter that the advertiser returns with a conversion. The push network click identifier serves a separate purpose: returning an event to that network. PropellerAds uses ${SUBID}, while Kadam and Push.house use {click_id}. An arbitrary query parameter does not automatically become a recognized external ID. Save the network value in a chosen sub field for analysis. The general outgoing adapter cannot substitute sub fields, so saving the value alone does not configure event return. Do not send the internal clickid as a replacement. Verify both values on one test journey, including the landing page button.
Know which costs can be imported
inotrack has cost clients for PropellerAds, Kadam, ExoClick, TrafficStars, Evadav and Push.house. They are included in hourly synchronization and fetch campaign and placement statistics. This is support for particular APIs, not automatic import for every push network. These clients were implemented from API documentation; live account verification is not confirmed. There are no cost clients for Clickadu, RichAds, RollerAds or Galaksion, so use manual amount or CPC accounting. Apply the same approach to other unsupported networks. Check period, currency, campaign matching and import success rather than relying on a connection appearing in a list. Avoid manually duplicating synchronized spend.
Return events through HTTP
Push uses the general custom_http outgoing adapter. First configure the advertiser postback so that clickid, status, amount, currency and transaction are recorded correctly. Outgoing delivery needs a documented network endpoint and compatible parameters. The adapter supports {ext_click_id}, but not sub field macros, and arbitrary push click identifiers are not automatically recognized on incoming links. A ready conversion return connection cannot therefore be promised for every push network. The receiving service defines the request method and parameter names; there is no single endpoint for every network. Check the delivery response and the destination account event. A general adapter does not imply that every network accepts conversions or uses them for optimization. Keep secrets out of advertisement URLs and personal data out of zone or creative labels.
Investigate zones, protection and caps
Compare zones within one source using clicks, unique visits, conversions, costs and financial results. Begin with a shared short period and sufficient data, checking postback and import delays before judging placement quality. Bot filtering and antifraud checks provide additional signals. Inspect rejected requests separately in the blocking report and record changes to protection settings because these can affect recorded traffic totals. Offer caps limit participation in the flow and allow a fallback route. They are separate from advertising account spending limits. Test cap behavior, fallback availability and the alternative offer link so that destination problems are not incorrectly attributed to the entire network.
Questions
Does every push network support automatic cost import?
No. Only specific cost clients are implemented. Use manual amount or CPC accounting for other networks.
Why does a network reject the conversion?
Check endpoint requirements and the HTTP template. The outgoing adapter cannot substitute sub fields, and the internal clickid does not replace the network identifier.
Read next
More in this section
Run inotrack on your own server
One command on a clean VPS, 10–15 minutes. Get your key right after you pay on the site, or a free one for 7 days.
Questions? Message us on Telegram: @SmokeJung.