Ecommerce tag tracking allows you to measure the transactions and revenue that each Vibes campaign generates. Now, you can enable this feature for your push broadcasts. By adding this feature, you can track engagement from your push broadcasts, as well as track revenue.

Learn more about some potential behavioral targeting scenarios here.

🚧

Watch for double texts

If you already have SMS Cart Recovery set up, please note that in-app cart abandonment may also trigger an SMS reminder. Learn more about Cart Recovery here.

Step 1: Update your SDK, if necessary.

Before you begin, make sure your app is using a version of the SDK that is compatible with push ecommerce tags. See the compatible versions below:

• iOS: Version 4.6.0 & later
• Android: Version 4.8.0 & later

Step 2: Add product action tagging

To learn the behavior of your users, the first step is to link each action to a product object. The product object will pass the details of the product that your user interacted with to our analytics, allowing you to see what products were interacted with via your app.

The actions that we will be defining are:

• Click: When a user selects a product in your app.
• Add: When a user adds a product to their cart. Required for Cart Recovery.
• Detail: When a user chooses to view more details about a product.

Please include all three product actions in your app.

📘

Linking action to push messages

By default, each action is linked to the most recent push message that a user clicked on, represented by its activityUid. The developer can optionally specify the specific push activityUid to link the tracking action to.

Click

This SDK function records when a user clicks on a product.

Android

CHOOSE ONE

public void trackClick(@NonNull Product product, final VibesListener<Void> completion);

OR

public void trackClick(@NonNull Product product, @Nullable String activityUid, final VibesListener<Void> completion);

iOS

public func trackClick(product: Product, activityUid: String? = nil, completion: TrackProductActionCallback?)

Add

This SDK function records when a user adds a product to their cart.

Android

CHOOSE ONE:
 
public void trackAdd(Product product, final VibesListener<Void> completion);
 
OR
 
public void trackAdd(Product product, String activityUid, final VibesListener<Void> completion); 

iOS

public func trackAdd(product: Product, activityUid: String? = nil, completion: TrackProductActionCallback?)

Detail

This SDK function records when the user chooses to view more details about a product.

Android

CHOOSE ONE:
 
public void trackDetail(Product product, final VibesListener<Void> completion);
 
OR
 
public void trackDetail(Product product, String activityUid, final VibesListener<Void> completion);

iOS

public func trackDetail(product: Product, activityUid: String? = nil, completion: TrackProductActionCallback?)

Step 3: Add purchase related tracking

In addition to details about each product, you will want to include tags to track purchases made that are related to your push notification. Each action also requires the passing of a Purchase object, representing details of the purchase the end user made via your app.

📘

Linking action to push messages

By default, each action is linked to the most recent push message that a user clicked on, represented by its activityUid. The developer can optionally specify the specific push activityUid to link the tracking action to.

Purchase

This SDK function records when a purchase is made by the end user.

Android

CHOOSE ONE:
 
public void trackPurchase(Purchase purchase, final VibesListener<Void> completion);
 
OR
 
public void trackPurchase(Purchase purchase, String activityUid, final VibesListener<Void> completion);

iOS

public func trackPurchase(purchase: Purchase, activityUid: String? = nil, completion: TrackProductActionCallback?)

Step 4: Create your push broadcast

Once you’ve completed the setup steps, there are no additional steps to take to add tag tracking to your push campaigns. However, we recommend you sent a test broadcast to verify that the tags are properly firing. After you’ve sent up the test broadcast as normal, reach out to your account representative and confirm that the data is being collected.

Please note that these analytics are not retroactive, and data will only be collected from campaigns set up after you have completed the above steps.

📘

Associating action to push notifications

Data will always be associated with the most recently sent push notification. This association will not expire until you send another push notification.