ScaleBun
Skip to article

Campaigns

Administrator

Campaigns in the Marketing area (Acquisition) — route /marketing/campaigns.

Updated Reviewed

Campaigns lives in the Marketing area of the dashboard, under Acquisition.

At a glance#

Dashboard route/marketing/campaigns
AreaMarketing (marketing)
GroupAcquisition
PlatformsAvailable for every app platform.

What it does#

Campaigns are first-class objects here — you create them in the dashboard rather than having them exist only as a string in a UTM parameter — and each one is shown merged with its attributed performance: installs, revenue and status.

That merge is the reason the page exists. A campaign you defined and a campaign name that arrived in a link are the same record, so a typo in a link does not silently create a second campaign nobody planned.

When to use it#

At the start of any campaign, before the links are built. Defining the campaign first means every link, every report and every conversation uses the same name — which is the entire difference between a usable channel report and a list of near-duplicate strings.

Workflow#

  1. Create the campaign before creating the links

    Then build links from it — see Links. Naming discipline is impossible to retrofit.

  2. Use a naming convention and write it down

    spring-sale-2026-instagram scales. Spring Sale and spring_sale and SpringSale are three campaigns.

  3. Read installs alongside revenue

    A campaign with high installs and no revenue is worse than one with fewer of both, because you paid for the volume.

  4. Then compare at channel level

    Channels aggregates campaigns. Campaign-level noise resolves there.

Permissions and prerequisites#

Requires attribution to be working for performance data to appear. A campaign can be created before that, and will simply have no numbers.

Limits and edge cases#

  • Campaign names arriving in links are matched literally. Case and punctuation differences create separate entries and cannot be merged retroactively.

  • Performance depends on attribution coverage, which undercounts — see the attribution page for why.

  • Revenue is client-reported with the usual caveats.

  • A campaign with no attributed installs may still have run. Absence here is not proof it did not deliver.

Troubleshooting#

Duplicate-looking campaigns. Different strings arrived in links. Fix the links; the existing records cannot be combined.

Campaign exists with no data. Either attribution is not matching, or the links do not carry the campaign parameter.

Installs but no revenue. Check whether revenue events are being attributed at all — Revenue attribution reports the unattributed share.

Where the data comes from#

Served by

  • Engage

  • Engage delivery

Campaigns · Marketing · Dashboard · ScaleBun