How to connect EZmob to RedTrack for real-time campaign tracking

Instead of manually matching ad spend to affiliate conversions, connect EZmob traffic to a RedTrack campaign URL, pass the tracking identifier into your offer, and return conversions through the generated postback. This RedTrack campaign tracking integration guide covers the click path, conversion feedback, and checks you need before using the reports to change bids.

Why this matters

A conversion total is not enough to decide which inventory deserves your next bid. You need the conversion attached to the campaign and source information captured when the visitor arrived. Otherwise, profitable and unprofitable traffic end up in the same report.

EZmob self-serve advertising is best for media buyers who want to launch pop, push, display, and native campaigns themselves. The benefit is control over campaign setup; the responsibility is validating the tracking path before treating its reports as buying signals.

For your 2026 setup, distinguish event tracking from cost reporting. A working conversion postback proves that a conversion reached the tracker, not that spend, revenue, and attribution are all correct. The same separation applies in the related Voluum conversion-tracking guide, but use RedTrack's own generated configuration for this workflow.

Before you start

• Have advertiser access to EZmob and permission to configure campaigns in RedTrack. Prepare your destination, approved offer materials, and access to the affiliate network or conversion system that will send the postback. New advertising campaigns go through creative moderation before going live.
• Confirm that your offer accepts a tracking identifier and that its conversion system can return that same value. Also confirm that your landing page, if used, preserves tracking parameters when visitors continue to the offer.
• Separate the tracker click identifier from the traffic-source click identifier. The tracker needs its own identifier to attribute the conversion; a postback sent back to the ad network needs the source identifier. Substituting one for the other breaks the return path.

Use the configuration supplied by your active accounts in 2026, including supported macros, parameter names, and generated endpoints. Copy those values rather than typing syntax from memory. Treat a traffic-source template as a starting configuration that still needs a live test.

Traffic-source configuration

The traffic-source configuration tells RedTrack which information an incoming advertising click carries. Start with attribution, not automatic bidding or cost synchronization. Keep this first setup narrow enough that you can inspect every value passed through it.

1. Create or select the traffic-source configuration for your advertiser account. If an applicable template exists, inspect its parameter mappings before using it; otherwise, configure the source using the macros documented in the advertiser account.
2. Map the source click identifier separately from campaign and placement identifiers. Add only identifiers that the traffic source actually supplies, using the tracker configuration's designated fields or supported custom parameters.
3. Decide how campaign cost will enter the report. Use a supported cost connection or documented cost parameter where available; otherwise, reconcile spend separately. Do not enable an assumed automatic cost connection simply because conversion tracking works.

Expected result: the traffic-source configuration identifies the origin of the visit without confusing source identifiers, tracker identifiers, or cost values.

A useful naming convention distinguishes format, offer, and GEO. Keep those names consistent between the buying account and tracker so you can match reports without relying on memory. Naming helps reconciliation, but it does not replace passing identifiers through the URL.

Offer and postback configuration

The offer configuration connects the tracked visit to the conversion system. The critical handoff is the tracker click identifier: it must reach the offer and come back unchanged with the conversion. A campaign name is not a substitute.

1. Add the actual offer destination to the tracker configuration. Identify the offer's documented parameter for accepting a tracking value, then insert the tracker-generated click identifier using RedTrack's supported substitution syntax.
2. Generate the conversion postback from the tracker configuration. Put it into the affiliate network or conversion system that records the completed action, replacing the relevant identifier placeholder with that system's documented return token.
3. Configure revenue and event information only when the conversion system supplies those values. Check the expected currency and event meaning before mapping them. Do not label every returned event as an approved, payable conversion.

Expected result: the conversion system stores the tracker identifier received with the visit and returns it to the correct tracker endpoint when the configured event occurs.

The tracker click identifier must survive the entire offer journey. Check this handoff before adjusting campaign targeting. A visitor reaching the right page does not prove that the identifier arrived with the visit.

For a 2026 implementation, retain a configuration record containing the parameter mapping, event definition, and currency convention. Exclude credentials and personal visitor data. This record makes later troubleshooting possible without reconstructing the original setup.

Campaign URL and destination configuration

Choose the destination path according to how the offer works, not according to which setup looks shorter. A landing page adds a handoff to inspect; direct-to-offer routing removes that handoff but also removes your pre-offer page.

1. Create the RedTrack campaign using the configured traffic source and offer. Add the landing-page route if your workflow requires it, and verify that its onward destination uses the tracker's supported tracking method.
2. Copy the generated campaign tracking URL into the advertiser campaign's destination configuration. Keep the supplied parameter syntax intact. Do not replace it with the final offer URL, which would bypass the configured tracking entry point.
3. Inspect the saved destination and the complete redirect path. Confirm that the eventual landing page or offer is correct and that required parameters remain present at each relevant handoff.

Expected result: an advertising visit enters the tracker campaign before reaching the intended destination, with the configured source information attached.

The basic sequence is Traffic source, Tracker campaign, Offer destination, and Conversion postback. Each part has a distinct job: originate the visit, record its identity, receive the visitor, and return the conversion event.

Do not use a copied tracking URL from a different campaign as a shortcut. Even when the destination matches, the campaign association and source mappings can differ. Generate the URL from the configuration you intend to measure.

Validation and reporting configuration

A visible destination page is only the first validation check. You also need evidence that the tracker recorded the visit and associated the returned event with that visit. Complete this check before using CPA to exclude inventory.

1. Send a permitted test visit through the exact campaign destination you saved. Inspect the recorded visit for campaign association, the tracker identifier, and supported source parameters. A manually opened URL checks routing, but not necessarily expansion of advertising macros.
2. Use the offer system's permitted test procedure to send a conversion. Confirm that the returned identifier matches the recorded visit and that the event appears under the intended campaign. Keep test activity separate from production performance analysis.
3. Reconcile spend, event totals, revenue, timezone, and currency across the relevant systems. Confirm what each report counts before comparing it: a submitted event, an approved conversion, and a paid conversion are different reporting definitions.

Expected result: you can trace a permitted test from its source visit to its recorded conversion and explain the associated cost and revenue values.

For your 2026 launch, define what real-time reporting means operationally: an event should appear after the conversion system sends it and the tracker processes it. Real-time tracking is not a guarantee of instant conversion approval. Do not diagnose a missing approved conversion before confirming that the offer system actually sent the event.

Send conversions back to the traffic source

An adjacent workflow sends attributed conversions from RedTrack back to the advertising account. This is separate from receiving conversions in RedTrack, and it requires a supported conversion endpoint on the traffic-source side.

1. Obtain the conversion endpoint and accepted parameters from the advertiser account's current tracking instructions.
2. Configure the tracker to return the original traffic-source click identifier, not its own click identifier, using the supported outgoing postback configuration.
3. Choose the event that should trigger the return postback. Use a clearly defined event rather than sending every stage of the offer funnel as the same conversion.
4. Test the return path and check that the advertiser account associates the event with the correct campaign or visit.

Expected result: the advertiser account receives the intended event with an identifier it recognizes, where that tracking connection is supported.

Receiving conversions in the buying account does not establish automatic optimization. Treat event reporting, cost synchronization, and automated bid changes as separate capabilities, each requiring its own configuration and verification.

If you change the offer's event definition later, review both postback directions. A new event can produce correct tracker records while making the advertising account's conversion totals incomparable with earlier results.

Troubleshooting

Visits appear, but conversions do not

Inspect the identifier received by the offer and the identifier returned in the postback. They must match the tracker visit you are investigating. Check whether the conversion system sent the event at all before rebuilding the campaign.

If the identifier is missing, repair the offer parameter or landing-page handoff. If it is present, inspect the conversion system's postback delivery record and the tracker response using the diagnostics available in those accounts.

Placement values contain literal macro text

A source macro that remains unchanged has not supplied a usable placement value. Check its spelling, the format's supported macros, and whether the visit came from the actual advertising delivery path rather than a manually opened URL.

Replace unsupported parameters with documented ones. Do not rename literal macro text into a placement label and then use it to make inventory decisions.

The offer loads, but the click identifier disappears

Inspect the landing-page onward link and intermediate redirects. A redirect that drops the relevant query parameter can preserve the visible destination while breaking attribution.

Repair the handoff that loses the value, then repeat the permitted test. Adding a conversion pixel elsewhere does not repair a missing identifier in a server-to-server return path.

Conversion totals differ between reports

Compare event definitions, timezone, approval status, and reporting windows first. Then inspect whether repeated notifications refer to the same conversion and whether the systems' supported duplicate-handling configuration matches your event model.

Do not assume the larger total is correct. Reconcile identifiable events before excluding traffic or changing bids.

CPA is wrong even though attribution works

Check whether cost is present, current, and assigned to the correct campaign. Also inspect currency and revenue mappings. Correct conversion attribution cannot repair an unrelated spend import or a currency mismatch.

Hold cost-based optimization until the cost calculation is reconciled. You can validate the conversion path independently while correcting the financial reporting.

Customize your workflow

Once the basic path works, expand reporting around decisions you can actually make. Capture supported placement identifiers for inventory analysis, separate meaningful funnel events, and keep format and GEO labels consistent. Add dimensions deliberately rather than collecting parameters without a buying use.

For EZmob campaigns, compare performance within a consistent format, GEO, and event definition before changing bids. Pop and push represent different delivery formats; combining them into a single undifferentiated report hides which campaign configuration produced the result.

Your 2026 workflow should also include a change log. Record destination changes, parameter edits, event-definition changes, and cost-connection changes alongside campaign edits. When reporting shifts, that history helps distinguish a traffic result from a tracking change.

FAQ

One last thing

A successful page load can hide a broken tracking setup. The destination can look right while the identifier needed for attribution has already disappeared. Save a permitted, traceable test record before your 2026 launch so later configuration changes have a known working reference.

Related guides

• Keitaro postback tracking setup
• Popunder traffic for affiliate marketers
• Ecommerce popunder campaign case studies

Ready to launch with a validated tracking path? Start advertising on EZmob.