Acquisition targeting

Acquisition targeting serves a different onboarding funnel (or an A/B test of funnels) depending on which ad drove the install. Rovenue records where each install came from, lists the campaigns it has seen, and lets you map a campaign, ad set or ad to an onboarding from one page, without an app update.

It is built on placements: the Campaigns page manages one onboarding placement, and every mapping becomes an audience row in that placement.

Where attribution comes from

Attribution is write-once per subscriber: the first record wins and later reports for the same install change nothing. An install with no ad behind it is organic, and organic users get the placement's default onboarding.

Acquisition settings

Open Acquisition › Settings. Only a project owner can open or change this page, because the key and the URLs on it are secrets.

• Onboarding placement - the placement the Campaigns page manages. Mapped campaigns write their rows into it. Changing it later does not move existing rows; mapping a campaign again moves its row.
• Meta Install Referrer Decryption Key - copy it from the Meta App Dashboard: Settings › Basic › Android. It is stored encrypted and only its last four characters are shown again. Paste a new key to replace it, or remove the stored one.
• Apple Search Ads - turn on to attribute iOS installs through Apple's AdServices token.
• AppsFlyer push URL and Adjust callback URL - generated when you save. Copy them into the MMP (see AppsFlyer and Adjust server-to-server).
• Advenue webhook URL - Rovenue registers it with Advenue itself; it is shown for the manual setup.

Rotate the postback URLs issues new ones and invalidates the old ones at once; paste the new URLs into the MMP before relying on the backup path again. The Advenue URL is re-registered automatically.

The Campaigns page

Acquisition › Campaigns lists what Rovenue has actually seen in the last 7 days of installs. There is no manual entry: a campaign appears once an install arrives with attribution naming it. The one exception is Advenue: with an Advenue connection, the campaigns Advenue knows are listed before the first install (marked From Advenue), so you can map them up front and the first installs already get the mapped onboarding.

• The list is a tree: Network › Campaign › Ad set › Ad, with install counts.
• New campaigns that are not mapped yet raise a NEW banner. Map the campaign, or dismiss the banner to keep the default onboarding.
• Pick an onboarding for any node: a funnel, an experiment over funnels, Default, or Nothing (no onboarding).
• Networks also show a Campaign unknown node for installs of that network that named no campaign. You can map it like any other node.
• Organic installs are not mappable; they see the default.
• Mappings whose campaign no longer appears in the install data are listed under Unavailable campaigns; Unmap removes their rows.

What a mapping writes

Mapping a node writes a managed audience and a row for it in the onboarding placement. Both are locked: the row is locked in the placement editor and the managed audience is read-only. Change or remove them from the Campaigns page, not by editing the placement. You can also build your own audiences from the Acquisition group of conditions (network, campaign, ad set, ad, organic or non-organic) for rules the page does not cover.

Most specific wins

When an install matches several mappings, the most specific one is served:

ad › ad set › campaign › network

A network-level "Campaign unknown" row only catches installs of that network that named no campaign; it does not shadow campaigns you mapped explicitly.

Web funnels

A web funnel visit captures the ad click ids fbclid, ttclid, gclid and gbraid and the utm_* query parameters, and attributes the session the same way an install is attributed. Name your ad URLs with this convention so the tree fills correctly: