Basic and Re-Targeting Campaign

EMMA gives you the possibility to work with two modalities of tracking links according to the campaign goals. 

Basic Campaign

The Basic campaigns modality attributes the activity of the devices that have never had the app  and continue doing it during the user's life without any attribution window limit. 

The main objective of this campaign type is to impact users who have never had the app and to know all the attributed activity to the origin of the install event regardless of the spent time.

Use cases

Now, it will be shown different attribution examples:

1. The device has never had the app and click on a Basic source:

The user clicks on a Basic source and installs the app

A click and an install are counted in the source reporting.

On day 20 the user opens the app and registers in it

A session and a register event are counted in the Basic source.

On day 380 the user opens the app and makes a purchase

A session and a conversion event are counted in the Basic source.

2. The device has already had the app and click on a Basic source (B source) different from the origin source of the install (A source):

The user clicks on a Basic source different from the install origin, opens the app and makes a login

A click is counted in the Basic B source and a session and a login in the Basic A source.

Re-Targeting Campaign

The Re-targeting campaigns modality attributes the activity of devices that have never had the app and also those devices that have it during a limited attribution window. 

The attribution window establishes the maximum time that could pass between a click and an event (install or in-app) to assign it in the Apptracker.

The main objective of this campaigns is to re-impact users who have already had the app, so we can attribute certain in-app activity after the interaction with this type of tracking links. 

Use cases

Now, it will be shown different attribution examples:

1. The device has never had the app and click on a Re-Targeting source with a 30 day attribution window:

On day 1 the user clicks on a Re-Targeting source and installs the app

A click, an engagement and an install are counted in the source reporting.
On day 30 the user opens the app and registers A session and a register event are counted in the Re-Targeting source.
On day 31 the user opens the app and makes a conversion

A session and a conversion event are counted in the user's historic* but not in the Re-Targeting source.

* The user's historic is always accesible in the Behavior section form the different options of the reporting.

2. The device has never had the app and click on a Re-Targeting source (A source) with a 30 day attribution window and after that, the user clicks on another Re-Targeting source with 4 day attribution window (B source)

On day 1 the user clicks onthe Re-Targeting source A and installs the app

A click, an engagement and an install are counted in the source A reporting.

On day 2 the user opens the app and registers

A session and a register event are counted in the A Re-Targeting source.

On day 3 the user clicks on the Re-Targeting source B, opens the app and makes a conversion

A click, an engagement, a session and a conversion are counted in the Re-Targeting source B. A session and conversion event are counted in the user's historic* but not in the Re-Targeting source A.

* The user's historic is always accesible in the Behavior section form the different options of the reporting.

3. The device has already had the app and click on a Re-Targeting source with a 14 day attribution window:

On day 1 the user clicks on a Re-Targeting source

A click and an engagement are count in the source reporting.

On day 3 the user opens the app and registers

A session and a register event are counted in the Re-Targeting source as in the installation attribution source (classic or organic).

On day 15 the user opens the app and makes a conversion

A session and a conversion event are counted in the installation attribution source (classic or organic) but not in the Re-Targeting source.

4. The device has already had  the app and click on a Re-Targeting source with a 2 day attribution window (source A) and after that, clicks on another Re-Targeting source with a 4 day attribution window (source B):

On day 1 the user clicks on the Re-Targeting source A and opens the app

A click, an engagement and a session are counted in the source A reporting. A session is counted in the installation attribution source (classic or organic).

On day 2 the user opens the app and registers

A session and a register event are counted in the installation attribution source (classic or organic) but not in the Re-Targeting source A.

On day 3 the user clicks on the Re-targeting source B, opens the app and makes a conversion

A click, an engagement, a session and a conversion are counted in the Re-Targeting source B reporting. A session and a conversion are counted in the installation attribution source (classic or organic).

On day 7 the user opens the app and logs in

A session and a login are counted in the Re-Targeting source B as in the installation attribution source (classic or organic).

On day 8 the user opens the app and makes a conversion

A session and a conversion are counted in the installation attribution source (classic or organic) but not in the Re-Targeting source.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.