Skip to content
  • There are no suggestions because the search field is empty.

Best Practices for Setting Up Opensend Reconnect Scenarios on Bloomreach

To help brands fully capitalize on Opensend Reconnect 2.0, we recommend implementing four strategic Bloomreach Scenarios designed to re-engage high-intent, anonymous shoppers through precise, event-triggered messaging. These include:

  • Session Abandonment, which targets users who viewed products but took no action
  • Product Abandonment, engaging those who showed product-level interest without adding to the cart
  • Cart Abandonment Reminder flow, nudging cart abandoners who didn’t initiate checkout
  • Checkout Abandonment scenario, focused on recovering users who started—but didn’t complete—the checkout process

Each scenario leverages Opensend-specific custom events, strict cross-provider filters, and dynamic email paths tailored to buyer status, ensuring maximum personalization, deliverability, and conversion.

General Notes

  • Bloomreach Scenarios: For triggers use Opensend-specific Events
  • Filtering: Strict exclusion of events from the default scenarios and other similar tools tracking events/metrics
  • In campaign settings, select General consent and “Enabled (all clicks) option for Transfer identity to URL links option

 

Configuring Entry Rules (Global Suppressions):

  • Entry Rules determine who is allowed to enter a scenario.
  • Use cases include:
  • Preventing users who already completed a purchase from re-entering
  • Avoiding conflict with similar event-based journeys from other tools
  • Enforcing cool-down periods

Implement a waterfall across all abandonment scenarios, placing Opensend Reconnect where appropriate. Time delays, filters, and entry rules should be configured accordingly.

Personalize Journey Templates by using Reconnect Event Payload

Personalize journey templates using dynamic content from the Opensend Reconnect event payload.


Bloomreach Opensend Reconnect Scenario Best Practices

🔄 1. Session Abandonment Scenario (Opensend Reconnect)

To implement this scenario, we recommend either cloning your existing Scenario for the same event and adjusting the configuration as outlined below, or creating a new scenario from scratch.

1.1 Trigger:

Drop the On event element onto your scenario canvas and select “Opensend Reconnect Device Profile Detected” from the Events.

1.2 Filtering Contacts:

  • Drag Condition element onto your scenario canvas.
  • Open the Condition settings and choose Select customers → not matching → funnel.
  • Set the Funnel completion period to Last 24 hours.
  • In Step 1, select campaign as the event type.
  • Add condition:
    • campaign_id → equals → Enter your campaign ID
    • (You can copy the campaign_id directly from the URL of your scenario — it appears in the address bar when the scenario is open.)
  • Add another condition:
    • action_id → in → Enter the relevant action IDs for your email steps
  • Add another condition:
    • status → equals → delivered
  • Add the final condition:
    • action_type → equals → email
  • Make sure all conditions are connected with AND.
  • Click Done to save the Conditional Split configuration.

The same logic should be applied to the campaigns for each of the following events:

Default Events: 

  • Added to Cart, Viewed Product, Started Checkout, Active On Site

Other tools metrics:

  • Tool 1: Active On Site, Viewed Product, Added to Cart, Checkout Started
  • Tool 2: Active On Site, Viewed Product, Added to Cart, Checkout Started
  • Similarly, excluding metrics from any other identity providers you are using

Other Opensend Reconnect metrics:

  • Opensend Reconnect Device Profile Detected, Opensend Reconnect Viewed Product, Opensend Reconnect Added to Cart, and Opensend Reconnect Started Checkout

Last cart update & no purchase Condition:

  • Add a Conditional Split.
  • Configure logic: A AND NOT B
  • A (matching → attribute)
    • [OACO] Last cart update timestamp → equals → 0
  • B (not matching → funnel | Lifetime)
  • Event: purchase
    • timestamp → greater than → [OACO] Last cart update timestamp
    • purchase_status → in → success, invoiced
  • Click Done.

1.3 Wait:

Drop the Wait element onto your scenario canvas and set “2 Hours”

1.4 Scenario Dynamic Content Update:

For the Session Abandonment Email, no e-commerce event data will be used or accessible. Default email templates should be used as currently configured.

1.5 Set Flow Live ✅

🛍️ 2. Browse/Product Abandonment Scenario (Opensend Reconnect)

To implement this scenario, we recommend either cloning your existing Scenario for the same event and adjusting the configuration as outlined below, or creating a new scenario from scratch.

2.1 Trigger:

Drop the On event element onto your scenario canvas and select “Opensend Reconnect Viewed Product” from the Events.

2.2 Filtering Contacts:

  • Drag Condition element onto your scenario canvas.
  • Open the Condition settings and choose Select customers → not matching → funnel.
  • Set the Funnel completion period to Last 24 hours.
  • In Step 1, select campaign as the event type.
  • Add condition:
    • campaign_id → equals → Enter your campaign ID
    • (You can copy the campaign_id directly from the URL of your scenario — it appears in the address bar when the scenario is open.)
  • Add another condition:
    • action_id → in → Enter the relevant action IDs for your email steps
  • Add another condition:
    • status → equals → delivered
  • Add the final condition:
    • action_type → equals → email
  • Make sure all conditions are connected with AND.
  • Click Done to save the Conditional Split configuration.

The same logic should be applied to the campaigns for each of the following events:

Default Events: 

  • Added to Cart, Viewed Product, Started Checkout

Other tools metrics:

  • Tool 1: Viewed Product, Added to Cart, Checkout Started
  • Tool 2: Viewed Product, Added to Cart, Checkout Started
  • Similarly, excluding metrics from any other identity providers you are using

Other Opensend Reconnect metrics:

  • Opensend Reconnect Viewed Product, Opensend Reconnect Added to Cart, and Opensend Reconnect Started Checkout

Last cart update & no purchase Condition:

  • Add a Conditional Split.
  • Configure logic: A AND NOT B
  • A (matching → attribute)
    • [OACO] Last cart update timestamp → equals → 0
  • B (not matching → funnel | Lifetime)
  • Event: purchase
    • timestamp → greater than → [OACO] Last cart update timestamp
    • purchase_status → in → success, invoiced
  • Click Done.

2.3 Wait:

Drop the Wait element onto your scenario canvas and set “90 Minutes”

2.4 Scenario Dynamic Content Update:

To ensure your Opensend Reconnect emails display personalized content correctly, please find below a few examples of dynamic variables you can use in your email content:

  • Product Image URL: {{item.image_url}}
  • Product Title: {{item.item_name}}
  • Product Price: {{item.price}}

2.5 Set Flow Live ✅

🛒 3. Cart Abandonment Scenario (Opensend Reconnect)

To implement this scenario, we recommend either cloning your existing Scenario for the same event and adjusting the configuration as outlined below, or creating a new scenario from scratch.

3.1 Trigger:

Drop the On event element onto your scenario canvas and select “Opensend Reconnect Added to Cart” from the Events.

3.2 Filtering Contacts:

  • Drag Condition element onto your scenario canvas.
  • Open the Condition settings and choose Select customers → not matching → funnel.
  • Set the Funnel completion period to Last 24 hours.
  • In Step 1, select campaign as the event type.
  • Add condition:
    • campaign_id → equals → Enter your campaign ID
    • (You can copy the campaign_id directly from the URL of your scenario — it appears in the address bar when the scenario is open.)
  • Add another condition:
    • action_id → in → Enter the relevant action IDs for your email steps
  • Add another condition:
    • status → equals → delivered
  • Add the final condition:
    • action_type → equals → email
  • Make sure all conditions are connected with AND.
  • Click Done to save the Conditional Split configuration.

The same logic should be applied to the campaigns for each of the following events:

Default Events: 

  • Added to Cart, Started Checkout

Other tools metrics:

  • Tool 1: Added to Cart, Checkout Started
  • Tool 2: Added to Cart, Checkout Started
  • Similarly, excluding metrics from any other identity providers you are using

Other Opensend Reconnect metrics:

  • Opensend Reconnect Added to Cart, and Opensend Reconnect Started Checkout

Last cart update & no purchase Condition:

  • Add a Conditional Split.
  • Configure logic: A AND NOT B
  • A (matching → attribute)
    • [OACO] Last cart update timestamp → equals → 0
  • B (not matching → funnel | Lifetime)
  • Event: purchase
    • timestamp → greater than → [OACO] Last cart update timestamp
    • purchase_status → in → success, invoiced
  • Click Done.

 

3.3 Wait:

Drop the Wait element onto your scenario canvas and set “1 Hour”

3.4 Scenario Dynamic Content Update:

To ensure your Opensend Reconnect emails display personalized content correctly, please find below a few examples of dynamic variables you can use in your email content:

  • Product Image URL: {{item.image_url}}
  • Product Title: {{item.item_name}}
  • Product Price: {{item.price}}

3.5 Set Flow Live ✅

🧾 4. Checkout Abandonment Scenario (Opensend Reconnect)

To implement this scenario, we recommend either cloning your existing Scenario for the same event and adjusting the configuration as outlined below, or creating a new scenario from scratch.

4.1 Trigger:

Drop the On event element onto your scenario canvas and select “Opensend Reconnect Started Checkout” from the Events.

4.2 Filtering Contacts:

  • Drag Condition element onto your scenario canvas.
  • Open the Condition settings and choose Select customers → not matching → funnel.
  • Set the Funnel completion period to Last 24 hours.
  • In Step 1, select campaign as the event type.
  • Add condition:
    • campaign_id → equals → Enter your campaign ID
    • (You can copy the campaign_id directly from the URL of your scenario — it appears in the address bar when the scenario is open.)
  • Add another condition:
    • action_id → in → Enter the relevant action IDs for your email steps
  • Add another condition:
    • status → equals → delivered
  • Add the final condition:
    • action_type → equals → email
  • Make sure all conditions are connected with AND.
  • Click Done to save the Conditional Split configuration.

The same logic should be applied to the campaigns for each of the following events:

Default Events: 

  • Started Checkout

Other tools metrics:

  • Tool 1: Checkout Started
  • Tool 2: Checkout Started
  • Similarly, excluding metrics from any other identity providers you are using

Other Opensend Reconnect metrics:

  • Opensend Reconnect Started Checkout

Last cart update & no purchase Condition:

  • Add a Conditional Split.
  • Configure logic: A AND NOT B
  • A (matching → attribute)
    • [OACO] Last cart update timestamp → equals → 0
  • B (not matching → funnel | Lifetime)
  • Event: purchase
    • timestamp → greater than → [OACO] Last cart update timestamp
    • purchase_status → in → success, invoiced
  • Click Done.

4.3 Wait:

Drop the Wait element onto your scenario canvas and set “30 Minutes”

4.4 Scenario Dynamic Content Update:

To ensure your Opensend Reconnect emails display personalized content correctly, please find below a few examples of dynamic variables you can use in your email content:

  • Product Image URL: {{item.image_url}}
  • Product Title: {{item.item_name}}
  • Product Price: {{item.price}}

4.5 Set Flow Live ✅

Note:

  • When you are done creating all scenarios with Opensend Reconnect events and are ready to use the Opensend Reconnect, go back to the Opensend dashboard and find your Bloomreach Reconnect flow setup
  • Paste all of the created scenario IDs from previous step to the Scenario IDs for Reconnect field (You can find your scenario IDs in scenario URL as shown below:
  • When you are done copying and pasting, your setup should look like this: