In December 2024 we improved the way Ometria associates product data from mobile apps with individual stores.
The new mobile app SDK will change the way stores are ingested, and there are a few things you'll need to do to upgrade your app and take advantage of these multi-store capabilities.
What's changed?
Ometria's new mobile app SDK supports multiple stores.
This means that retailers with multiple stores can integrate all of their stores into their mobile app and send Ometria website interaction/visit events.
How does Ometria associate products with stores?
When a contact makes a visit to one of your store sites, their visit data is associated with the appropriate store, e.g. the UK store or US store.
In Ometria, products can exist across multiple different stores.
When you send a message triggered by website interaction data, e.g. abandoned browse, abandoned basket, etc. and that message references products (in merge tags, product recommendations, etc.) then Ometria tries to fetch the right product from the right store.
For example, if Jane was browsing for a pair of boots in a UK store and received an abandoned browse email encouraging her to purchase a specific pair of boots, Ometria tries to show the product variant for the UK store.
If a product can't be found in the UK store, Ometria won't use it.
Mobile app visits
Until December 2024, all visits from mobile apps were associated with a 'default' store, rather than the specific store in which the visit occurred.
Because of this limitation, we asked retailers to set up their mobile app to send products assigned to the 'default' store, so that you could still use product data in your marketing messages.
What should I do?
If your mobile app is currently integrated with Ometria and you'd like to to use this new functionality (i.e. multi-stores), you need to:
- Make sure all of the stores you want to use in your app also exist in Ometria.
- Make sure that the products you want to use are sent to the right stores.
Finally, speak to your app development team about integrating with the new version of our mobile app SDKs:
Your development team should set the store IDs for visits, but they must not deploy this change to production until you've completed the steps above.
Keep the 'default' store
The pre-December 2024 app version sends visits to 'default' until the app user updates their version.
Be aware that the rollout of the new version of your app may take some time to reach the majority of your app users - and some of them might never update.
For this reason, you should keep the products in your 'default' store for the time being.
Comments
0 comments
Article is closed for comments.