Jacquard's Bloomreach integration leverages our cutting-edge Dynamic Optimisation technology. Dynamic Optimisation powers real-time optimisation by evaluating and reacting to how your subscribers are responding to language during a deployment. This ensures the best-performing language reaches the widest possible audience.

Before we begin this process, make sure you've got your Jacquard Connect Server token handy. If you don't have one, your Jacquard admin can create one for you by following these instructions.

To get these Jacquard and Bloomreach talking to each other correctly, we'll need to set up three Bloomreach integrations and a Scenario. Let's start with HTTP Authentication Schemas.

This integration will handle the authentication of the real-time endpoint call Bloomreach will make to Jacquard.

Essentially, it's preprogramming a password of sorts for Bloomreach to use when reaching out to Jacquard for your language variants.

On the left side of your screen in Bloomreach, hover over Data & Assets and then click Integrations.

Click Add new integration.

Click the Authentication tag on the left and then hover over HTTP Authentication Schemas and click Add integration.

Start by giving the integration a unique name. In the example below, we have used Jacquard Realtime In-App HTTP Auth.

For the Endpoint, you should use the following:

https://realtime.phrasee.co

Then, select the Custom headers option. Under Key, type Authorization.

For the Value, you should type Bearer and then a single space. After the space, paste your Jacquard Connect Server token.

Now, set the Type to public.
​

When you're done, it should look something like the below:

Now, click Save integration in the upper-right corner.

The second Bloomreach integration we need to set up is the Webhook preset. This is the technology that will actually pass your language variants from Jacquard to Bloomreach.

Head back to the Integrations section we were in before. Click the Webhook tag on the left, hover over Webhook preset and click Add integration.

Again, start by giving your integration a unique name. We have used Jacquard Get In-App Variant in the example below.

Now, it's time to complete the settings.

Selecting an Icon is optional, as is adding a Description.

Leave the Preset type set to Normal Webhook.

Scroll down and choose GET under Endpoint URL. Then, enter the following exactly as written in the text field:

https://realtime.phrasee.co/single_variant?campaign_id=[[phrasee_campaign_id]]&recipient_id={{customer_ids.registered | hash('sha1')}}&delivery_id={{scenario.id}}{{time | from_timestamp('%y%m%d')}}

Enable the Authentication toggle and choose the HTTP Authentication method you set up in the previous step. You'll recall we named ours Jacquard Realtime In-App HTTP Auth for this example.

For Response processing, choose Process response as JSON from the dropdown.

You will also have to create a Throughput policy at this point. Toggle the Throughput policy switch on. Then, click the gear that appears.

We've chosen Realtime API for the Policy name in our example. Set the Concurrency limit to 100.

Your settings should now look like the following:

Finally, choose whichever Consent category is appropriate according to your internal business rules and Bloomreach setup.

When you're finished, click Save integration in the upper-right corner.

Now, we'll create our final integration. Head back to the Integrations section we were in before. Click the Data sources tag on the left, hover over Amazon S3 for Exports and click Add integration.

Give your integration a unique name. We chose Jacquard In-App Amazon S3 for Exports.

Fill out all of the required fields using the credentials provided to you by your Jacquard representative. If you don't yet have credentials, please reach out to your Customer Success representative and ask for credentials to be created for you.

Click Save integration in the upper-right corner when you're finished.

In the upper-right corner of your Bloomreach window, click on the Settings gear.

Then, click Project settings in the dropdown menu.

In the project settings window, expand the General option under the Campaign Settings subhead.

Under the Custom campaign tracking heading, click the Add custom attribute button.

You'll be adding five of these custom attributes. For each, you'll need to enter the Custom attribute name, Default value and uncheck the Editable option. Everything else, you can leave alone.

Use the following for the custom attributes' names and default values:

You'll be adding seven custom attributes in total. It should look like this when you're finished:

When everything is configured correctly, click Save changes in the upper-right corner.

Remember, you'll only need to do this part once per Bloomreach project.

Hover over the Data & Assets menu and click Exports.

Click the + New export button in the upper-right corner.

Give your export a unique name. We've chosen Jacquard Export for our example. Then, click Events to choose the export type.

Select campaign from the Events to export dropdown menu.

Click Add an event attribute.

Click action_type from the menu that appears.

Set action_type equal to the channel you want to export: app inbox for in-app or and browser notification for web push.

Click Refine more.

Choose timestamp from the menu that appears.

Set timestamp equal to less than 12 minutes ago.

Click Next in the bottom-right corner.

Ensure every field is checked to send in the export. Click Next, again.

Under Format, ensure you select the following:

Under Target, ensure you select or enter the following:

When you're finished, your settings should resemble the following:

Click Next, again. under Schedule execution of export, select the following options:

To set all of the 10-minute intervals, click Add minutes to receive another textbox.

This sets a repeated export to run at 10-minute intervals in perpetuity. It should look like the below when you're done.

Click Run export in the bottom-right corner to finish your setup.

With this completed, your integration is setup. All that's left to do is set up the Scenarios for your individual broadcast or trigger experiments.

Page last reviewed: 25 March 2025