Skip to main content

Creating an event tracking plan for your mobile app

Louise
  • Updated
This is the first step you should take when integrating your mobile app with Ometria. Click here for a full list of integration steps.

It’s a good idea to create a plan that defines the events you want to track based on the marketing journeys you’d like to create.

This should be used in your brief to your development team. 

For further information on these events please refer to the relevant SDK docs on github.

Note: The SDK tracks some events automatically, but there are other events which must be configured by your development team - these are manually tracked events.

Required to track manually:

Customer identified - an app user has just identified themselves, i.e. logged in.

  • trackProfileIdentifiedEvent (customerId: String)
  • trackProfileIdentifiedEvent (email: String)

See also: Identifying customers on mobile

Note: If you use customer ID to identify your contacts, it's very important that the `customerId` above matches the customer_id passed for the contact record. If they don't match, Ometria won't be able to identify your contacts, and you won't be able to market to them.

Suggested events

Customer journey

Events to track

App abandoned app basket
  • trackBasketUpdatedEvent(basket: OmetriaBasket)
  • trackBasketViewedEvent()
  • EventCheckoutStarted
  • orderCompleted

App abandoned app product browse
  • trackProductViewedEvent(productId: String)

Price drop

App abandoned category browse
  • trackProductListingViewedEvent(listingType: String?, listingAttributes: [String: Any]?)

Placed an order
  • trackOrderCompletedEvent(orderId: String, basket: OmetriaBasket)

For any other use cases where events trigger marketing journeys you can use custom events using the following SDK call:

trackCustomEvent(customEventType: String, additionalInfo: [String: Any]?)

Or, alternatively, you can send custom events via our push objects endpoint.

See also: Setting up custom events

Define order channels

It's important that you define different order channels in the Order endpoint of our data API, e.g. online, in store, mobile app.

These can be used to segment contacts, report on behaviour and trigger campaigns.  

Related articles

Comments

0 comments

Article is closed for comments.