Setup

Configure The Wallet Crew connector, connect Bloomreach credentials, and install the Bloomreach WebHook preset activities.

Connect Bloomreach Engagement with The Wallet Crew to orchestrate wallet journeys. Bloomreach scenarios can trigger pass actions (create, update, notify). The Wallet Crew also sends events back to Bloomreach for segmentation and measurement.

A minimal end-to-end setup typically takes 1 to 2 hours. This assumes access rights and a test pass are available to validate the flow.

Prerequisites

Before starting, make sure you have:

• Bloomreach permissions

  • Access to Project settings → Integrations.
  • Access to API credentials under Project settings → Access Management → API.
• The Wallet Crew permissions

  • Access to the admin console to configure the Bloomreach connector.
  • Permission to create and manage API keys.
• Environment and test data

  • Target environment identified (staging vs production).
  • A test pass exists, with a known passId, to validate calls end-to-end.
  • Any required network allowlisting and security constraints are in place.

The Wallet Crew configuration

1

Enable the connector

The Bloomreach connector must be enabled for the tenant. This is typically done by The Wallet Crew team.

2

Configure general settings

Open the Bloomreach connector settings in the Wallet Crew back-office.

Open General settings page

General settings define how The Wallet Crew authenticates to Bloomreach.

Fill in:

• Project Token
• API Base Url
• API Key Id
• API Secret

Bloomreach values are available under Project settings → Access Management → API.

Project Token determines the target environment. This makes it possible to keep staging and production separated.

Use a token and API key scoped to the correct Bloomreach environment.

3

Advanced settings (extensibility)

Advanced settings expose script entry points for the connector. These scripts control contact resolution, event transformation, and field mapping.

Advanced settings are used for custom data models and governance.

Details and script examples: Extensibility.

Bloomreach configuration

1

Set up an HTTP authentication schema

Bloomreach calls The Wallet Crew APIs using an API key. This is configured once as an HTTP authentication schema in Bloomreach.

In Bloomreach:

1. Go to Data & Assets → Integrations → + Add new integration.

1. Select Http Authentication Schemas.

1. Configure the schema with an API key created in The Wallet Crew.

A The Wallet Crew API key with tenant.pass:write permission is required. API keys are managed in the Wallet Crew admin console.

Open API Keys configuration

Bloomreach schema values:

Endpoint	https://app.neostore.cloud/api (production) or https://app-qa.neostore.cloud/api (staging)
Type	Custom headers
Key	X-API-KEY
Value	The Wallet Crew API Key

2

Install the WebHook preset activities

Bloomreach activities are installed as WebHook preset integrations. One Bloomreach integration is typically created per activity.

Only the needed activities should be installed. This keeps scenario building simple and reduces configuration drift.

Activity icons are available as a file:

6KB

twc-bloomreach-icons.zip

archive

Open

Payload examples use Bloomreach WebHook preset parameter syntax.

Update pass ("Push Update")

Endpoint URL:

PATCH https://app.neostore.cloud/api/<<tenantId>>/passes/?id=[[ {name: 'passId', tooltip: 'Identifier of the pass', category: 'Pass target', isJsonParam: true} : string]]

Minimum payload (options only):

{
  "options": {
    "correlationId": "[[ {name: 'Correlation Id', tooltip: 'Grouping identifier to associate multiple actions', category: 'Advanced configuration', orderIndex: 20, isJsonParam: true} : string]]"
  }
}

Example payload to update additionalData:

{
  "additionalData": {
    "xx": "[[ {name: 'xx', tooltip: 'xx', category: 'Content', orderIndex: 10, isJsonParam: true} : string]]",
    "xy": "[[ {name: 'xy', tooltip: 'xy', category: 'Content', orderIndex: 11, isJsonParam: true} : string]]"
  },
  "options": {
    "correlationId": "[[ {name: 'Correlation Id', tooltip: 'Grouping identifier to associate multiple actions', category: 'Advanced configuration', orderIndex: 20, isJsonParam: true} : string]]"
  }
}

Example payload to change the pass template (passType):

{
  "passType": "newTemplate",
  "options": {
    "correlationId": "[[ {name: 'Correlation Id', tooltip: 'Grouping identifier to associate multiple actions', category: 'Advanced configuration', orderIndex: 20, isJsonParam: true} : string]]"
  }
}

API reference: API reference.

Notify

Endpoint URL:

PATCH https://app.neostore.cloud/api/<<tenantId>>/passes/notification?id=[[ {name: 'passId', tooltip: 'Identifier of the pass', category: 'Pass target', isJsonParam: true} : string]]

Example payload (single language):

{
  "content": "[[ {name: 'Notification Content', tooltip: 'Content of the notification', category: 'Content', orderIndex: 10, isJsonParam: true} : string]]",
  "options": {
    "updateData": [[ {name: 'Update data', tooltip: 'Also update pass data when notification is sent', category: 'Advanced configuration', orderIndex: 20, isJsonParam: true} : boolean | false]],
    "correlationId": "[[ {name: 'Correlation Id', tooltip: 'Grouping identifier to associate multiple actions', category: 'Advanced configuration', orderIndex: 20, isJsonParam: true} : string]]"
  }
}

Example payload (localized):

{
  "localizedContent": {
    "en": "[[ {name: 'Notification Content (en)', tooltip: 'Content of the notification', category: 'Content', orderIndex: 10, isJsonParam: true} : string]]",
    "fr": "[[ {name: 'Notification Content (fr)', tooltip: 'Content of the notification', category: 'Content', orderIndex: 11, isJsonParam: true} : string]]"
  },
  "options": {
    "updateData": [[ {name: 'Update data', tooltip: 'Also update pass data when notification is sent', category: 'Advanced configuration', orderIndex: 20, isJsonParam: true} : boolean | false]],
    "correlationId": "[[ {name: 'Correlation Id', tooltip: 'Grouping identifier to associate multiple actions', category: 'Advanced configuration', orderIndex: 20, isJsonParam: true} : string]]"
  }
}

API reference: API reference.

Apply privilege

Endpoint URL:

POST https://app.neostore.cloud/api/<<tenantId>>/passes/[[ {name: 'passId', tooltip: 'Identifier of the pass', category: 'Pass target', isJsonParam: true} : string]]/privileges

Payload example (unlocalized privilege):

{
  "type": "multiUse",
  "origin": {
    "generator": "bloomreach",
    "processId": "[[ {name: 'Process identifier', tooltip: 'Identifier of the scenario / campaign', category: 'Advanced configuration', orderIndex: 120, isJsonParam: true} : string]]"
  },
  "priority": [[ {name: 'Priority', tooltip: 'High values mean stronger priority', category: 'Advanced configuration', orderIndex: 110, isJsonParam: true} : number]],
  "content": {
    "title": {
      "value": "[[ {name: 'Title', tooltip: 'Title of this privilege', category: 'Content', orderIndex: 10, isJsonParam: true} : string]]"
    },
    "description": {
      "value": "[[ {name: 'Description', tooltip: 'Description of this privilege', category: 'Content', orderIndex: 20, isJsonParam: true} : string]]"
    }
  },
  "appearance": {
    "mainImageUrl": {
      "value": "[[ {name: 'Main Image', tooltip: 'Url of the main image', category: 'Content', orderIndex: 30, isJsonParam: true} : image]]"
    }
  },
  "options": {
    "correlationId": "[[ {name: 'Correlation Id', tooltip: 'Grouping identifier to associate multiple actions', category: 'Advanced configuration', orderIndex: 130, isJsonParam: true} : string]]"
  }
}

API reference: API reference.

Endpoints include <<tenantId>>. Replace it with the tenant identifier of The Wallet Crew.

To know more about activities : Bloomreach activities.

Validation checklist

A minimal validation run usually covers:

• One test pass exists and its passId is available in Bloomreach.
• One Update pass activity refreshes visible content on the pass.
• One Notify activity delivers a message.
• One test install/uninstall produces Bloomreach events.

Event names and properties: Events.

Best practices

• Staging first: validate activities and events in a test Bloomreach project token.
• Progressive rollout: install only Notify first, then add Apply privilege.
• Multi-team setup: IT configures credentials and allowlists, marketing installs the scenario activities.

FAQ

Who typically owns Setup?

Connector enablement and credentials are typically owned by IT or an implementation partner. Activity installation and scenario usage are often owned by CRM or marketing operations.

Which environment should be set up first?

A staging environment is usually set up first. This makes it possible to validate activities, events, and scripts before production.

Which permissions are required for the API key used by Bloomreach?

A key with tenant.pass:write permission is required for activities that update passes. Additional permissions can be required depending on the activity set.