Vero
Send Encatch survey events to Vero - where to find the details in Vero and how to set up the connection
Overview
The Vero connector sends survey events to a Vero project as tracked events on the user, ready to trigger campaigns and build segments.
| What it gets | Survey events as tracked events on the user |
| Events | Survey shown, started, submitted, partially submitted and dismissed |
| Anonymous respondents | Not sent: identified users only |
| User profile | Not updated yet: events only |
| Status | Available |
What You'll Need
Before you start, make sure you have:
- A Vero project — Vero 2.0 or Vero 1.0
- A Tracking API key — from the project's settings (Step 1)
Step 1: Get your Tracking API key in Vero
- Vero 2.0: open Settings → Project → API Keys → Tracking Keys, create a key and copy it.
- Vero 1.0: open Settings → Track API Keys and copy the Auth token.
Step 2: Add the connection in Encatch
- In Encatch, open Data sync → Survey events and click Add connection.
- Choose Vero.
- Enter a Name you'll recognise in the list and in Logs.
- Fill in the Vero settings:
| Field | What to enter |
|---|---|
| Tracking API key | The tracking key (Vero 2.0) or Auth token (Vero 1.0). |
- Press Test connection. Encatch shows what Vero answered.
Encatch keeps the keys encrypted and never shows them again. To change one later, press Replace.
Step 3: Choose what to send
- Under Surveys, choose All surveys or Only these surveys.
- Under What is sent, tick the events to send. A new Vero connection starts with Survey submitted only, because Vero bills by event. Tick the other events if you want them.
- Rename an event if you want another name in Vero. The defaults are
encatch_survey_shown,encatch_survey_started,encatch_survey_submitted,encatch_survey_partialandencatch_survey_dismissed. - Open Advanced options to choose how users are identified, whether answers are sent and the rate limit.
Every option is explained in Connection settings.
Step 4: Save and start sending
Click Save. Saving does not start sending: press Start sending when you are ready. From then on events go out as they happen, and every delivery is listed in Logs.
Check it in Vero
Test connection sends one event named encatch_test_event. In Vero, open Data → Events: each survey event is listed under the name you chose. Its page shows the recent users and the properties after about a minute of processing. Profiles lists the user with their email.
Good to know
- Answers as text. Each answer is sent as its own text property,
answer_<key>, because Vero stores event data as text. - Event names. Vero treats upper and lower case, spaces and
_as the same, so two events cannot differ only by those. - New profiles. Vero creates a profile for any user ID it does not have yet.
- Events only. Vero gets the events; Encatch does not set user properties in Vero yet, so Update the user's profile is shown off.
- Billing. Events count toward your Vero plan's monthly event allowance.
- Rate limit. Vero sets its limits per customer and does not publish them: ask Vero for yours.
- Also send the email. Vero keeps the email in its own field next to the user ID. Turn the option on in Advanced options to send it.
Troubleshooting
| What you see | What it means | What to do |
|---|---|---|
| Key refused | The key is not a tracking key, or belongs to another project | Copy the Tracking key (or Auth token) again from the project's settings |
Was this page helpful?
