Vero

App · 8 actions

Keep your Vero customers up to date from your workflows: create and update profiles, track events that start journeys, add push devices, tag, rename, unsubscribe, resubscribe and delete customers.

Actions

ActionWhat it does
Add push deviceAdd a mobile device's push token to a customer, so Vero can send them push notifications.
Change customer IDChange the ID Vero knows a customer by.
Delete customerDelete a customer with all their properties and activity.
Edit customer tagsAdd tags to a customer, remove tags, or both in one step.
Identify customerCreate a customer in Vero, or update one it already has, with their email and profile properties.
Resubscribe customerSubscribe a customer who unsubscribed back to messages from Vero.
Track eventRecord something a customer did, such as a purchase, with its details.
Unsubscribe customerUnsubscribe a customer from all messages from Vero.

Add push device

Add a mobile device's push token to a customer, so Vero can send them push notifications. A customer can have several devices.

Inputs

Customer IDcustomer_idtextRequired
The customer's ID in Vero: the ID your app gave them, or their email if they were added with only an email.
Device tokendevice_tokentextRequired
The push notification token your mobile app received for this device.
PlatformplatformtextRequired
The device's operating system.One of: ios, android.

Outputs

customer_idtext
The customer's ID in Vero: the Customer ID given, or the email when only an email was given
device_tokentext
The push token added
messagetext
Vero's confirmation, such as Success.
platformtext
The device's platform
statusnumber
Vero's status for the request, 200 when accepted
Example output
{
  "customer_id": "1000",
  "device_token": "fcm-token-example",
  "message": "Success.",
  "platform": "android",
  "status": 200
}

Change customer ID

Change the ID Vero knows a customer by. If another customer already has the new ID, Vero merges the two profiles into one, which can have results you don't expect.

Inputs

Current customer IDcustomer_idtextRequired
The ID Vero knows the customer by now.
New customer IDnew_customer_idtextRequired
The ID to give the customer from now on. If another customer already has it, Vero merges the two profiles into one.

Outputs

customer_idtext
The customer's ID from now on
messagetext
Vero's confirmation, such as Success.
previous_customer_idtext
The ID the customer had before
statusnumber
Vero's status for the request, 200 when accepted
Example output
{
  "customer_id": "1001",
  "message": "Success.",
  "previous_customer_id": "1000",
  "status": 200
}

Delete customer

Delete a customer with all their properties and activity. Vero can't recover a deleted customer; tracking them again starts a new, subscribed profile.

Inputs

Customer IDcustomer_idtextRequired
The customer's ID in Vero: the ID your app gave them, or their email if they were added with only an email.

Outputs

customer_idtext
The customer's ID in Vero: the Customer ID given, or the email when only an email was given
deletedtrue/false
Always true once Vero accepts the request
messagetext
Vero's confirmation, such as Success.
statusnumber
Vero's status for the request, 200 when accepted
Example output
{
  "customer_id": "1000",
  "deleted": true,
  "message": "Success.",
  "status": 200
}

Edit customer tags

Add tags to a customer, remove tags, or both in one step.

Inputs

Customer IDcustomer_idtextRequired
The customer's ID in Vero: the ID your app gave them, or their email if they were added with only an email.
Tags to addadd_tagslist
Tags to give the customer. Use letters, numbers, hyphens and underscores. The tag unsubscribed unsubscribes them.
Tags to removeremove_tagslist
Tags to take off the customer.

Outputs

added_tagslist
The tags added
customer_idtext
The customer's ID in Vero: the Customer ID given, or the email when only an email was given
messagetext
Vero's confirmation, such as Success.
removed_tagslist
The tags removed
statusnumber
Vero's status for the request, 200 when accepted
Example output
{
  "added_tags": [
    "vip"
  ],
  "customer_id": "1000",
  "message": "Success.",
  "removed_tags": [
    "trial"
  ],
  "status": 200
}

Identify customer

Create a customer in Vero, or update one it already has, with their email and profile properties. Vero applies the change a moment later.

Inputs

Customer IDcustomer_idtext
The customer's unique ID, usually their user ID in your own app. Give this, the email, or both. With only an email, Vero uses the email as the ID.
Emailemailtext
The customer's email address. Give this, the Customer ID, or both.
Propertiespropertiesobject
Profile properties to set, by name and value, such as first_name or plan. A timezone property takes hours from GMT, such as -5. Properties you leave out keep their values.
Only update existing customersonly_update_existingtrue/false
Update the customer only if Vero already has them, and never create a new profile.Default: false.
Changed atchanged_atdate and time
When these values changed. Vero skips a value older than the one it already holds, so leave this empty unless you are sending past data, such as an import.

Outputs

customer_idtext
The customer's ID in Vero: the Customer ID given, or the email when only an email was given
emailtext
The customer's email, empty when none was given
messagetext
Vero's confirmation, such as Success.
statusnumber
Vero's status for the request, 200 when accepted
Example output
{
  "customer_id": "1000",
  "email": "jo@example.com",
  "message": "Success.",
  "status": 200
}

Resubscribe customer

Subscribe a customer who unsubscribed back to messages from Vero.

Inputs

Customer IDcustomer_idtextRequired
The customer's ID in Vero: the ID your app gave them, or their email if they were added with only an email.

Outputs

customer_idtext
The customer's ID in Vero: the Customer ID given, or the email when only an email was given
messagetext
Vero's confirmation, such as Success.
statusnumber
Vero's status for the request, 200 when accepted
subscribedtrue/false
Always true once Vero accepts the request
Example output
{
  "customer_id": "1000",
  "message": "Success.",
  "status": 200,
  "subscribed": true
}

Track event

Record something a customer did, such as a purchase, with its details. Vero creates the customer if it doesn't have them, and the event can start journeys and campaigns that send messages.

Inputs

Customer IDcustomer_idtext
The customer's unique ID, usually their user ID in your own app. Give this, the email, or both. With only an email, Vero uses the email as the ID.
Emailemailtext
The customer's email address. Give this, the Customer ID, or both.
Event nameevent_nametextRequired
The event's name, such as Purchased item. Vero treats capitals, spaces and underscores alike, so Purchased Item and purchased_item are the same event.
Propertiespropertiesobject
Details of the event, by name and value, such as product and price. Vero drops a repeat of the same event for the same customer with the same details within 5 minutes.
Occurred atoccurred_atdate and time
When the event happened. Leave empty for now.
Sourcesourcetext
Where the event came from, such as Shopify. Vero stores it with the event.

Outputs

customer_idtext
The customer's ID in Vero: the Customer ID given, or the email when only an email was given
emailtext
The customer's email, empty when none was given
event_nametext
The event tracked
messagetext
Vero's confirmation, such as Success.
statusnumber
Vero's status for the request, 200 when accepted
Example output
{
  "customer_id": "1000",
  "email": "jo@example.com",
  "event_name": "Purchased item",
  "message": "Success.",
  "status": 200
}

Unsubscribe customer

Unsubscribe a customer from all messages from Vero.

Inputs

Customer IDcustomer_idtextRequired
The customer's ID in Vero: the ID your app gave them, or their email if they were added with only an email.

Outputs

customer_idtext
The customer's ID in Vero: the Customer ID given, or the email when only an email was given
messagetext
Vero's confirmation, such as Success.
statusnumber
Vero's status for the request, 200 when accepted
unsubscribedtrue/false
Always true once Vero accepts the request
Example output
{
  "customer_id": "1000",
  "message": "Success.",
  "status": 200,
  "unsubscribed": true
}

On this page