Goal
Last updated
Last updated
With Goals, you can track and report certain behaviors that users take in your application. They group information about an event with extra details about how users trigger that event. These extra details include:
Conditions that filter out irrelevant instances of the event.
The number of times the goal is triggered for the event.
Together, this information records events with specific constraints so you can establish patterns, analyse user behaviours, and inform networks.
Limitation: Each company can only have 25 goals.
You use goals in a few places within the marketing pipeline:
First, when you create a campaign with a network, you may assign it a goal. For example, you might have a goal for users to install your app. Or, you might have a goal for users to make an in-app purchase.
When users view or click your ad, the network sends data to your tracking URL that includes a goalId.
After that, users are redirected to your application where they may trigger some events. The justtrack SDK sends those events to your account so you can analyse them.
If those events match one of your goals and you have an active postback configured for that goal, we trigger the postback to send attribution data to the network that ran the source campaign.
Why have a goal for your campaign? Usually, you only pay your network for a certain "conversion event". Therefore, we need to know what that event is. This way, we can calculate your marketing spend after we send the postback for that goal.
