Tracking Shopflo Checkout Events in CustomerLabs

Shopflo is a popular one-click checkout platform that helps improve e-commerce conversions. However, users often experience duplicated purchase counts and discrepancies in Meta Ads reporting due to duplicated pixel firing and browser limitations affecting client-side tracking.

By leveraging CustomerLabs’ first-party data (1PD) platform, businesses can implement server-side tracking via Meta’s Conversions API, overcoming Shopflo’s native tracking restrictions. This ensures more accurate event data, reduces data loss, and improves ad attribution and campaign optimization on Meta and Google Ads.

Prerequisites

• Active CustomerLabs Account
• Active Shopflo Account with checkout access
• Access to coordinate with your Shopflo Point of Contact (POC) or Shopflo Support Team to configure webhook delivery

Note

Unlike other one-click checkout platforms, Shopflo’s integration is webhook-based. Shopflo needs to push events directly to CustomerLabs via a webhook URL. You must contact the Shopflo team to set this up before proceeding.

Step 1: Create a Custom Source in CustomerLabs

Once you have informed the Shopflo team, set up the Custom Source in CustomerLabs to generate the Webhook URL.

1. Log in to your CustomerLabs account.
2. Navigate to Sources → Connect Source → Custom Source.
3. Name the source Shopflo Purchase.
4. A Webhook URL will be automatically generated. Copy this URL and share it with the Shopflo team (Next Step) so they can begin sending event data to CustomerLabs.

Tip

Learn more about setting up Custom Source webhooks: Custom Source (Webhook)

Step 2: Request Shopflo Team to Configure the Webhook

Before configuring anything on the CustomerLabs side, reach out to your Shopflo Account Manager or support team with the request to share the checkout_initiated, add_payment_info, order_placed events to the webhook URL generated in the previous step.

Tip

Email Template – Request to Shopflo Team:

We are onboarding with Customerlabs 1PD Ops. To enable accurate customer profiling and server-side event tracking, we require your assistance in sending the following checkout events to CustomerLabs via a webhook:

• checkout_initiated
• add_payment_info
• order_placed

Sharing the webhook URL <Insert Webhook URL> for the same.

Step 3: Verification of events received in the Webhook

Once Shopflo begins sending events to the webhook, verify that the events are received in the webhook.

1. Login to Customerlabs account.
2. Go to Monitoring → Logs. Click on Sources tab.
3. Choose “Shopflo Purchase” from Sources dropdown.
4. Choose the Time Range to “Last 1 day” and Click “Apply”.
5. Verify the events received in the webhook.
6. Ensure the customerlabs_user_id is present sent as a parameter in the payload. It is usually sent as cluid, user_id and starts with cl.

Step 4: Configure Workflows in CustomerLabs

Once Shopflo begins sending events to the webhook, configure a separate workflow in CustomerLabs for each event. Each workflow processes the raw webhook data and maps it to a CustomerLabs event.

Tip

Refer to Building a Workflow for a detailed guide on workflow setup.

Workflow 1: Checkout Made

1. Navigate to CustomerLabs → Sources → Shopflo Purchase.

2. Click “View Workflow List” at the top, then click “Create Workflow”.

3. Name the workflow Shopflo Checkout and set the workflow delay to 2 minutes.

4. In the Data Selection section, click “Fetch New Data” to load events that have been pushed to the webhook.

5. In the Filter section, add a condition:

   • Field: event_name
   • Condition: contains
   • Value: checkout_initiated

   Note

   Ensure the CustomerLabs User ID is present in the payload. This is required for profile unification across events.

6. In the Event Configuration section, select “Custom Event” and name it cl_shopflo_checkout_made.

7. In the User Identity Mapping section, map up to 3 user identifiers (e.g., identify_by_email, identify_by_phone). CustomerLabs will use these to build and unify the user’s 360° profile.

8. Under User Traits, map incoming attributes (e.g., first_name, last_name, city, state, zip_code). The more user details mapped, the higher the Event Match Quality (EMQ) on ad platforms like Meta.

9. Under Product Details, map e-commerce product attributes such as product_id, product_sku, product_variant, and product_quantity. Select line_items from the dropdown to map product arrays.

10. Under Event Properties, map the mandatory fields: value, currency, and transaction_id.

11. Click Save Workflow.

---

Workflow 2: Add Payment Info

Rather than creating a new workflow from scratch, clone the Checkout Made workflow and update only the filter and event name.

1. Navigate to CustomerLabs → Sources → Shopflo Purchase → Shopflo Checkout.
2. Click the three-dot menu (⋮) next to the Shopflo Checkout workflow and select “Clone”.
3. Rename the cloned workflow to Shopflo - Payment Info.
4. In the Filter section, update the condition to:
   • Field: event_name
   • Condition: contains
   • Value: add_payment
5. In the Event Configuration section, update the event name to cl_shopflo_add_payment_info.
6. Click Save Workflow.

---

Workflow 3: Purchased

1. Navigate to CustomerLabs → Sources → Shopflo Purchase → Shopflo Checkout.
2. Click the three-dot menu (⋮) next to the Shopflo Checkout workflow and select “Clone”.
3. Rename the cloned workflow to Shopflo - Purchase.
4. In the Filter section, update the condition to:
   • Field: event_name
   • Condition: contains
   • Value: order_placed
5. In the Event Configuration section, update the event name to Purchased.
6. Click Save Workflow.

---

Step 4: Verify Events in CustomerLabs

Once all three workflows are configured and Shopflo begins sending events, you can monitor them in the CustomerLabs Events Manager.

1. Navigate to CustomerLabs → Monitoring → Events Manager.
2. Select the relevant date range and click Apply.
3. Verify that the following events are being received successfully:
   • cl_shopflo_checkout_made
   • cl_shopflo_add_payment_info
   • Purchased