# Vero

> 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.

App · 8 actions. Web page: https://docs.lodol.com/docs/integrations/vero

## Actions

### 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 ID (`customer_id`, text, required): The customer's ID in Vero: the ID your app gave them, or their email if they were added with only an email.
- Device token (`device_token`, text, required): The push notification token your mobile app received for this device.
- Platform (`platform`, text, required): The device's operating system. One of: `ios`, `android`.

**Outputs**

- `customer_id` (text): The customer's ID in Vero: the Customer ID given, or the email when only an email was given
- `device_token` (text): The push token added
- `message` (text): Vero's confirmation, such as Success.
- `platform` (text): The device's platform
- `status` (number): Vero's status for the request, 200 when accepted

**Example output**

```json
{
  "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 ID (`customer_id`, text, required): The ID Vero knows the customer by now.
- New customer ID (`new_customer_id`, text, required): The ID to give the customer from now on. If another customer already has it, Vero merges the two profiles into one.

**Outputs**

- `customer_id` (text): The customer's ID from now on
- `message` (text): Vero's confirmation, such as Success.
- `previous_customer_id` (text): The ID the customer had before
- `status` (number): Vero's status for the request, 200 when accepted

**Example output**

```json
{
  "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 ID (`customer_id`, text, required): 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_id` (text): The customer's ID in Vero: the Customer ID given, or the email when only an email was given
- `deleted` (true/false): Always true once Vero accepts the request
- `message` (text): Vero's confirmation, such as Success.
- `status` (number): Vero's status for the request, 200 when accepted

**Example output**

```json
{
  "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 ID (`customer_id`, text, required): 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 add (`add_tags`, list): Tags to give the customer. Use letters, numbers, hyphens and underscores. The tag unsubscribed unsubscribes them.
- Tags to remove (`remove_tags`, list): Tags to take off the customer.

**Outputs**

- `added_tags` (list): The tags added
- `customer_id` (text): The customer's ID in Vero: the Customer ID given, or the email when only an email was given
- `message` (text): Vero's confirmation, such as Success.
- `removed_tags` (list): The tags removed
- `status` (number): Vero's status for the request, 200 when accepted

**Example output**

```json
{
  "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 ID (`customer_id`, text): 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.
- Email (`email`, text): The customer's email address. Give this, the Customer ID, or both.
- Properties (`properties`, object): 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 customers (`only_update_existing`, true/false): Update the customer only if Vero already has them, and never create a new profile. Default: `false`.
- Changed at (`changed_at`, date 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_id` (text): The customer's ID in Vero: the Customer ID given, or the email when only an email was given
- `email` (text): The customer's email, empty when none was given
- `message` (text): Vero's confirmation, such as Success.
- `status` (number): Vero's status for the request, 200 when accepted

**Example output**

```json
{
  "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 ID (`customer_id`, text, required): 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_id` (text): The customer's ID in Vero: the Customer ID given, or the email when only an email was given
- `message` (text): Vero's confirmation, such as Success.
- `status` (number): Vero's status for the request, 200 when accepted
- `subscribed` (true/false): Always true once Vero accepts the request

**Example output**

```json
{
  "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 ID (`customer_id`, text): 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.
- Email (`email`, text): The customer's email address. Give this, the Customer ID, or both.
- Event name (`event_name`, text, required): 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.
- Properties (`properties`, object): 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 at (`occurred_at`, date and time): When the event happened. Leave empty for now.
- Source (`source`, text): Where the event came from, such as Shopify. Vero stores it with the event.

**Outputs**

- `customer_id` (text): The customer's ID in Vero: the Customer ID given, or the email when only an email was given
- `email` (text): The customer's email, empty when none was given
- `event_name` (text): The event tracked
- `message` (text): Vero's confirmation, such as Success.
- `status` (number): Vero's status for the request, 200 when accepted

**Example output**

```json
{
  "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 ID (`customer_id`, text, required): 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_id` (text): The customer's ID in Vero: the Customer ID given, or the email when only an email was given
- `message` (text): Vero's confirmation, such as Success.
- `status` (number): Vero's status for the request, 200 when accepted
- `unsubscribed` (true/false): Always true once Vero accepts the request

**Example output**

```json
{
  "customer_id": "1000",
  "message": "Success.",
  "status": 200,
  "unsubscribed": true
}
```
