Vivenu CRM Integration with CustomerLabs 1PD Ops

Vivenu is a flexible ticketing platform that enables event organizers to manage ticketing, CRM, and marketing operations efficiently. By integrating Vivenu with CustomerLabs 1PD Ops, you can unify customer, ticketing, and transaction data to build enriched customer profiles.

---

Getting Started

Follow the steps below to seamlessly connect your Vivenu CRM account with CustomerLabs—no coding required.

---

Step-by-Step Guide to Configuring Events

Step 1: Log in to CustomerLabs

Sign in to your CustomerLabs account.

Step 2: Create a Custom Source

1. Navigate to Sources.
2. Select Custom Source.
3. Name it Vivenu CRM.
4. Copy the generated Webhook URL.

Step 3: Log in to Vivenu CRM

1. Sign in to your Vivenu account.
2. Navigate to the Webhooks section.
3. Create a new webhook.

Step 4: Configure the Webhook

1. Name the webhook (e.g., Purchase Configuration).
2. Select the event transaction.complete (represents a purchase event).
3. Enable additional events as needed.
4. Save the configuration.

Step 5: Test the Webhook

1. Perform a test purchase.
2. Verify if events are received in CustomerLabs under Sources → Vivenu CRM.

---

Workflow Setup in CustomerLabs

What is a Workflow?

A workflow transforms raw incoming data into structured event data using filters and mappings. It continuously processes and updates customer profiles in real time.

---

Step 6: Create a Workflow

1. Provide a workflow name (e.g., purchase_event or lead_created).
2. Set a workflow delay (recommended if multiple workflows exist to avoid duplicate user IDs).

Step 7: Choose Sample Data

1. Trigger an event (e.g., test transaction in Vivenu).
2. Fetch sample data in CustomerLabs.
3. Select a valid sample (ensure no null values in required fields).

Note

CustomerLabs does not process null values. Use actual values or empty strings ("") instead.

---

Step 8: Event Configuration

8.1 Event Name

• Choose Custom Event.
• Name the event (e.g., cl_purchase or as per your requirement).

Event Types:

• Custom Event – Define your own event name.
• Dynamic Event – Useful for lead stages (e.g., new deal closed).
• Create/Update User or Group – For CRM updates (Default events by CustomerLabs).

8.2 User Identity Mapping

Map identifiers to unify user data:

• Email
• Phone number
• Google Analytics Client ID
• Facebook FBP / FBC

This ensures accurate user tracking and improves audience matching.

8.3 Product Details

For eCommerce-related events:

• Add attributes like product ID, SKU, variant, size.
• Use line_items mapping.

8.4 Event Properties

Include key fields such as:

• Value
• Currency
• Transaction ID
• Order ID

---

Step 9: Save Workflow

Save the workflow after completing all configurations.

---

User Traits Mapping

Map user attributes like:

• Name
• Email
• Phone
• Address
• Lifecycle stage

This enables data activation in downstream tools like email platforms.

---

Logs & Debugging

Source Logs

• View all incoming events before processing.
• Includes raw JSON data.

Workflow Logs

• Shows how data is transformed and processed.
• Tracks errors and event flow.