Remerge Integration

Beta

The Remerge integration is still being verified with live advertiser accounts (the integration card shows a Beta badge). If adstage numbers differ from your Remerge dashboard, please let adstage support know.

In adstage you can collect cost data from Remerge app retargeting campaigns automatically, report clicks and conversions arriving through a tracking link under the remerge.ads channel, and send attributed installs and events back to Remerge. Cost collection is set up in the Cost Integration tab of Integrations > Ad Channel Integration > Remerge; tracking links and conversion sending are configured per link in Deep Links > Create.

1. Integration Overview

Remerge is a managed DSP. Campaign setup and link registration go through your Remerge account manager.

2. Setting Up Cost Collection

Before you start

Remerge does not issue a separate reporting API key. Enter the email and password you use to sign in to the Remerge dashboard. If you do not have a login, ask your Remerge account manager. Remerge's own documentation also authenticates the Reporting API with dashboard credentials and tells clients without a login to request one from their account manager.

Please note

We recommend creating a dedicated Remerge dashboard user for AdStage instead of using a team member's personal account. Collection stops if that person leaves or changes their password.

Steps

1. Open the Cost Integration tab in Integrations > Ad Channel Integration > Remerge. The How to get your Remerge key box and the Remerge reporting API documentation link at the top repeat the instructions. Since Remerge has no self-serve key page, the box shows Issued by your Remerge account manager.

2. Turn on the Remerge Cost Integration switch. While it is off, the Add Integration Account button is disabled.

3. Click Add Integration Account and fill in the Integration Information Registration dialog.

4. Click Integrate. Before saving, adstage signs in to Remerge with the credentials and pulls one day of report data (the button shows Verifying...). If that succeeds, the password is stored encrypted.

5. Once the account is added, the first collection starts immediately. Remerge reports must be requested one day at a time, so the first run can take a few minutes. The status shows Preparing until it finishes, then changes to Success.

Managing connected accounts

The account list shows Account Name, Status, Last Data Update, and Management (delete).

• Preparing: the first collection is still running.
• Success: Remerge API calls are working. The status stays successful even when no campaigns are running and no rows are returned.
• Failed: credentials changed or access was revoked, so no data could be fetched. Hover over the status to see the reason. adstage retries every cycle, so the status returns to Success automatically once the cause is fixed. Rate limits and temporary server errors do not flip the status; they are simply retried next cycle.

Even with a Success status, if no cost data is stored for more than three days a warning appears next to the status, and hovering shows "No cost data has been collected for N days". The warning clears automatically once data arrives again.

Credentials cannot be edited. If the password changed or you want to switch users, delete the account with the trash icon in the Management column and add it again. Deleting stops collection, but data already collected stays in adstage.

3. Creating Tracking Links

When someone taps a Remerge ad, Remerge sends them to the click URL registered for the campaign and fills in campaign and creative details plus the click ID. Register an adstage tracking link as that click URL so traffic and conversions land in the remerge.ads channel.

1. In Deep Links > Create, select Remerge as the ad channel.

2. The Campaign, Ad Group, and Creative fields are pre-filled with Remerge macros. Leave them as they are and Remerge substitutes the real names at click time.

3. To break out the publisher app and exchange as well, click Add channel details and fill in the Medium and Media Channel 1 fields.

4. Configure the redirect settings (app store, app, web), save, and copy the generated link.

5. Send the link to your Remerge account manager and ask them to register it as the click URL. There is no self-serve screen for this in the Remerge dashboard.

The link carries these macros. The click ID and the ID macros are always appended, even if you leave the name fields empty.

Example:

https://adg.im/@{org}/track/remerge.ads?short_path={link_path}&campaign={external_campaign_name_raw}&campaign_id={campaign}&ad_creative={ad_name}&ad_creative_id={creative}&sub_channel={publisher}&sub_channel_1={partner}&click_id={click_id}

Please note

• Do not remove or edit the macros in the link. Without the click ID, conversions cannot be matched to Remerge clicks and no postback can be sent.
• Do not type campaign names manually. Keeping the macro ensures the name Remerge fills in matches the campaign name from cost collection, so cost and conversions land on the same report row.
• Cost is collected at the campaign level only. Splitting a report by creative splits conversions while cost stays on the campaign row.

4. Sending Conversions to Remerge

Reporting attributed installs and events back to Remerge lets Remerge use them for retargeting optimization. This is configured per link under Network Postback. For shared behavior such as deduplication and retries, see Network Postback.

Before you start

• Ask your Remerge account manager for the partner name (partner) and key (key). Remerge assigns both.
• Register the Android Package Name and iOS Bundle ID under Tracking Link > Settings > Deep Link Settings. They fill the app_id parameter of the postback.

Steps

1. On the create or detail screen of a Remerge tracking link, turn on the Send install postback to ad network switch. For links whose ad channel is Remerge, the Remerge preset fills in automatically. If it does not, pick Remerge — Events (key from Remerge) under Network Preset.

2. Review the filled-in values. Installs and events use the same address, so leave Event Postback URL Template empty.

https://remerge.events/event?partner=adstage&key={auth_token}&app_id={bundle_id}&event={event}&idfa={idfa}&aaid={gaid}&ts={timestamp}&revenue_float={revenue}&currency={currency}&ip={ip}&is_attributed=1&partner_attribution_method=click&click_id={click_id}&campaign={campaign}

3. Paste the key from Remerge into the Network Auth Token field. It is stored encrypted and is never shown again.

4. Set Trigger Events. The default is install only. To send post-install events such as purchases, add them, and use Event Name Mapping if Remerge expects different names.

5. Save, then ask your Remerge account manager to confirm receipt. The Remerge Event Tracking API returns HTTP 204 by default, so only your account manager can verify that the values arrived correctly.

Please note

• app_id for iOS apps: Remerge's documentation expects the numeric App Store ID on iOS, but the preset fills app_id with the bundle ID from Deep Link Settings. For iOS apps, confirm with your account manager and replace app_id with the numeric App Store ID.
• Remerge's documentation also lists label (the creative label ID) as mandatory. It is not in the preset, so add it to the URL if your account manager asks for it.
• adstage only sends installs and events attributed to that link. Remerge prefers to receive unattributed (organic) events as well, but network postbacks carry attributed conversions only.
• If you use several links, configure the postback on each one.

5. Collected Data

Metrics reported by the network carry a (Channel) suffix in reports. Days with zero spend, impressions, and clicks are not stored.

6. Cautions

Please note the following.

• Remerge keeps report data for six months only. Older periods cannot be collected, so export reports separately if you need long-term comparisons.
• Numbers may differ between Remerge and adstage. adstage collects on UTC day boundaries, so viewing the Remerge dashboard in another timezone shifts daily figures.
• Campaigns can use different currencies. When a currency differs from the organization base currency, the converted amount is stored alongside it.
• Changing the password or deleting the Remerge user flips the status to Failed and stops collection.
• The current day is not collected. Reports show data through yesterday only.
• Traffic from custom links where the channel was typed as remerge is also reported under the remerge.ads channel.

7. Troubleshooting

The account cannot be added

1. Check the login: confirm the email and password sign in to the Remerge dashboard directly.
2. Check access: ask your account manager whether that user can view reports for the advertiser you are connecting.
3. Check for duplicates: confirm the same email is not already in the account list.
4. Connection error: "Could not reach Remerge" is a temporary Remerge-side issue. Try again shortly.

No data is being collected

1. Check the switch: confirm the Remerge Cost Integration switch is on.
2. Check the status: if it is Failed, hover for the reason; for authentication errors, delete the account and add it again.
3. Check delivery: if the status is Success but there is no data, spend, impressions, and clicks were all zero for that period. Check campaign status in the Remerge dashboard.
4. Check retention: Remerge has no data for periods older than six months.

Postbacks are not reaching Remerge

1. Check the link: confirm the ad click went through the adstage tracking link and that the click ID macro is still in the URL.
2. Check the key: confirm the Network Auth Token holds the key from Remerge and that partner matches the name Remerge assigned.
3. Check the bundle ID: confirm the package name and bundle ID are registered in Deep Link Settings, and whether app_id needs to be the numeric App Store ID on iOS.
4. Check trigger events: confirm the event you expect is listed under Trigger Events.
5. Ask your account manager: Remerge does not report success in the response, so ask them to reconcile what they received.

Cost and conversions appear on separate report rows

A link with a manually typed campaign name can diverge from the campaign name in Remerge. Switch to a link that keeps the macro in the campaign field.

8. Frequently Asked Questions

Do I need to request a separate API key?

No. Remerge has no separate reporting API key. Enter your dashboard login email and password. If you do not have a login, ask your Remerge account manager.

Conversions (Channel) and Installs (Channel) are empty in my report.

That is expected. Remerge conversions are retargeting target events, not app installs, so they are not counted as installs. Measure performance with Cost (Channel), Impressions (Channel), Clicks (Channel) and the event metrics adstage measures directly.

Is historical data from before the integration collected?

Up to the last 30 days from the moment you connect. Remerge itself keeps only six months, so nothing older can be collected by any means.

Can I register the tracking link myself in the Remerge dashboard?

No. Remerge is a managed DSP, so send the generated link to your account manager and ask them to register it.

9. Reference Documentation

• Remerge Reporting API — the API used for cost collection: sign-in authentication, six-month retention, response fields
• Click & Impression Placeholders — the click macros used in tracking links
• Event Data Forwarding — Event Tracking API endpoint and parameters, partner name and key issuance
• Attribution Data Forwarding — parameters required when sending attributed events