Send events to Vero via RudderStack web device mode.
3 minute read
RudderStack lets you send your event data to Vero via web device mode.
Identify
The identify call lets you identify a user and associate them to their actions. It also lets you record any traits about them like their name, email, etc.
The following table lists the mapping of the RudderStack traits to the corresponding Vero properties:
RudderStack trait
Vero property
Presence
userId/anonymousId
id
Required.
email
email
Optional
context.traits/traits
traits
Optional
email is an optional field. However, if it is absent, Vero will not be able to send any emails to the user, so it is recommended to have this trait in the event.
If userId is absent, RudderStack maps anonymousId to Vero’s id field to create or update the user.
Track
The track call lets you capture user events along with the properties associated with them.
You need to first create a user by explicitly calling identify before making any track calls to Vero. Otherwise, the track calls will fail.
Vero API does not differentiate between the upper or lower case letters, spaces, and underscores in the event names. For example, Vero matches the Purchased Item, purchased item, and purchased_item as the same event.
Supported mappings
The following table lists the mapping of the RudderStack properties to the corresponding Vero properties:
RudderStack property
Vero property
Presence
event
event_name
Required
properties
data
Optional
Unsubscribing and resubscribing users
RudderStack supports unsubscribing and resubscribing users in Vero by passing the userId in the track call:
The page call lets you record your website’s page views with any additional relevant information about the viewed page.
A sample page call is shown below:
rudderanalytics.page("Cart","Cart Viewed",{path:"/best-seller/1",referrer:"https://www.google.com/search?q=estore+bestseller",search:"estore bestseller",title:"The best sellers offered by EStore",url:"https://www.estore.com/best-seller/1"});
Alias
RudderStack sends the alias events to change a user’s identifier (id) in Vero.
A sample alias call is shown below:
rudderanalytics.alias("userId","previousId");
Supported mappings
The following table lists the mapping of the RudderStack properties to the corresponding Vero properties:
RudderStack property
Vero property
Presence
userId
new_id
Required
previousId
id
Required
Adding and removing tags
RudderStack supports adding and removing tags to all identify, track, and page calls by passing them via the integrations object. An example snippet is shown below:
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.