Goals

Goals in Mapp Intelligence are defined server‑side. They map a combination of pages, events, or parameter values to a measurable conversion (for example, "completed registration", "added 3+ items to cart", or "viewed pricing page"). The iOS SDK has no dedicated Goal API — instead, you populate the parameters that your account configuration uses to detect a goal.

How goals are tracked from the iOS SDK

1. Your account manager configures a goal in Mapp Intelligence and tells you which parameter number(s) the goal listens on (for example "session parameter 5" or "page parameter 12").

2. In your iOS app, set those parameter numbers via the matching MI…Parameters object on the page or action event when the user reaches the goal trigger.

3. Mapp Intelligence evaluates the goal definition against the incoming parameter values and counts the conversion.

Example: report a goal trigger via session parameter 5

Assume your account manager configured a goal that triggers when session parameter 5 is set to "signup_complete". Send this parameter when the user finishes the signup flow:

let pageEvent = MIPageViewEvent(name: "Signup Success")
pageEvent.sessionParameters = MISessionParameters(dictionary: [
    5: "signup_complete"
])
MappIntelligence.shared()?.trackPage(pageEvent)

MIPageViewEvent *pageEvent = [[MIPageViewEvent alloc] initWithName:@"Signup Success"];
pageEvent.sessionParameters = [[MISessionParameters alloc] initWithDictionary:@{
    @5: @"signup_complete"
}];
[[MappIntelligence shared] trackPage:pageEvent];

E‑commerce goals

Order‑value or revenue‑based goals usually rely on the e‑commerce data attached to a page event. See Products and Orders.

Always coordinate goal tracking with your customer success manager or account configuration team. Sending the wrong parameter or value can either miss conversions or count them multiple times.

Related: Pages, Events, Sessions, Products and Orders.