Bloomreach Integration FAQ

Q: Is the Bloomreach integration one-way or two-way?

A: It can be fully two-way. TRIFFT sends loyalty events to Bloomreach through Bloomreach's Customer Events API, while Bloomreach Scenarios can call TRIFFT REST APIs through HTTP authentication and webhook presets.

Q: Which Bloomreach credentials are required for TRIFFT to send events?

A: You need the Bloomreach API Base URL, Project Token, API Key, and API Secret from the correct Bloomreach project.

Q: Which Bloomreach API permissions are required?

A: Enable GET and SET permissions for both Customer Properties and Events in the private Bloomreach API group used by TRIFFT.

Q: Why does Bloomreach return HTTP 200 but the event is missing from the customer profile?

A: The webhook request may have been accepted while the customer identifiers were not recognized. Confirm that the keys and values in customer_ids match the Hard ID and/or Soft ID configuration in the Bloomreach project.

Q: What endpoint is used for TRIFFT events sent to Bloomreach?

A: Event webhooks normally use the Bloomreach API Base URL with /customer/events appended. The suffix may be stored in the TRIFFT authorization endpoint or in the individual webhook endpoint.

Q: Can event names and payloads be customized?

A: Yes. Bloomreach event names, properties, identifiers, and project-specific Custom Parameters can be adapted. Existing production event names should not be renamed without also updating the Scenarios, reports, and audiences that use them.

Q: Which identifier should I use in customer_ids?

A: Use the exact identifier names configured in Bloomreach. Common examples include email_address and a project-specific TRIFFT loyalty ID such as trfft_loyalty_id, but the correct mapping depends on the Bloomreach project.

Q: How can Bloomreach call a TRIFFT API?

A: Create a dedicated API key in TRIFFT, create an HTTP Authentication Schema in Bloomreach with Authorization: Bearer YOUR_KEY, and then create reusable Bloomreach webhook presets for the required TRIFFT endpoints.

Q: Should the TRIFFT API key have Read and Write access?

A: The legacy full-integration setup enables both. For production, use only the permissions required by the planned Scenarios whenever the available permission model allows it.

Q: When should I use TRIFFT batch or bulk APIs?

A: Use them for large audiences or operations such as adding thousands of members to a segment. Thousands of simultaneous individual webhook requests are less reliable and can overload the API.

Q: Why did a Bloomreach reward Scenario issue the same reward twice?

A: Check Scenario re-entry rules, duplicate event triggers, webhook retries, missing eligibility conditions, and whether the TRIFFT action is idempotent. Add frequency restrictions or a rewarded-state check before the webhook action.

Q: What is the difference between a segment/topic push and a one-to-one push?

A: A segment/topic push sends one uniform message efficiently to many members. A one-to-one push calls the member notification endpoint separately for each member and supports personalized content.

Q: Can a topic push contain the member's first name or individual reward details?

A: No. Use a one-to-one push when the message needs per-member values such as name, tier, balance, coupon, or reward details.

Q: Why are personalized push notifications delayed or duplicated?

A: Large simultaneous sends can cause TRIFFT API pressure, Apple or Google throttling, and Bloomreach retries. Distribute requests using wait nodes, A/B splits, cascaded branches, and controlled batches.

Q: How quickly can I send personalized one-to-one pushes?

A: Do not send more than a few hundred personalized pushes per minute without coordinating the expected load. Transactional pushes triggered one by one are generally safer than a large campaign blast.

Q: Why is a Bloomreach Weblayer not visible in the TRIFFT Web Portal?

A: Confirm that Client Zone tracking is enabled in Settings → Integrations → Bloomreach → Settings → Tracking, the Weblayer is active, the test customer belongs to the audience, and the Client Zone is correctly initialized.

Q: Why is Bloomreach content not visible in the TRIFFT Mobile App?

A: Confirm that the app is version 2.1.5 or higher, the Bloomreach campaign is active, the member belongs to the audience, and the Placeholder ID in Bloomreach exactly matches the Placeholder ID in the TRIFFT content block.

Q: Is there fallback content when the Placeholder IDs do not match?

A: No. If the IDs do not match, the Bloomreach content does not render. A short delay after page load is normal even when the configuration is correct.

Q: Do I need a new app release every time the Bloomreach In-App content changes?

A: No. Once the Bloomreach content block and Placeholder ID exist in the app layout, Bloomreach can control the content, audience, variants, and timing without publishing a new app version for each campaign change.

Q: Why did the Welcome Scenario not start?

A: Confirm that Bloomreach received the member-verification event, the customer identifiers resolved correctly, the Scenario is active, and the duplicate-control condition allows the customer to enter.

Q: How do I prevent a member from receiving the Welcome Scenario more than once?

A: Add a condition that checks whether the verification event or the Scenario has already been triggered for the member, and configure appropriate re-entry rules.

Q: Why did the birthday reward not trigger?

A: Confirm that the birthdate exists in a usable format, the daily Scenario ran, the birthday condition compares month and day correctly, and the webhook contains a valid TRIFFT member ID and reward configuration.

Q: Can I send the birthday message before the actual birthday?

A: Yes. Build the audience or schedule the Scenario to trigger two or three days before the birthday, then assign the reward and coordinate email, push, or Weblayer communication.

Q: Why did the Tier Up email not send?

A: Confirm that the tier-related event or segment update reached Bloomreach, the Scenario recognizes the new tier name, and the customer entered the correct Silver, Gold, or other tier branch.

Q: How do I avoid sending an NPS email after every purchase?

A: Add a frequency condition. The documented example waits 30 minutes after a transaction and suppresses the email when the customer received the same NPS communication during the previous seven days.

Q: Which event starts the documented post-purchase NPS Scenario?

A: The legacy example uses trft_transaction_challenge, sent after a TRIFFT transaction is created.

Q: What is required for Bloomreach push on iOS?

A: Configure an Apple Push Notification Service integration with the Team ID, Key ID, complete .p8 private key, and app Bundle ID, then assign that integration under the Bloomreach iOS push channel settings.

Q: What format must the Apple private key use?

A: Paste the entire key including -----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY-----.

Q: What is required for Bloomreach push on Android?

A: Configure a Firebase Cloud Messaging integration using the correct Firebase service-account credentials/private key, then assign it under the Bloomreach Android push channel settings.

Q: Why should Firebase credentials be changed carefully?

A: Replacing or regenerating the active key can invalidate the previous configuration and interrupt push delivery. Coordinate the change with the mobile-development team.

Q: How should I test APNs or Firebase setup?

A: Create a small test Scenario, add a Mobile Push node, use a test member with a valid platform push token, run the Scenario, and confirm delivery on the physical device.

Q: Can Bloomreach assign a TRIFFT coupon or add points?

A: Yes. Create the appropriate TRIFFT webhook preset and call it from a Bloomreach Scenario. Apply eligibility and duplicate-prevention logic before the action.

Q: Can Bloomreach add a member to a TRIFFT segment?

A: Yes. Use a TRIFFT segment API webhook. For large audiences, use the relevant batch or bulk operation instead of simultaneous individual requests.

Q: What should I check when a webhook returns an error?

A: Check the destination URL, HTTP method, authorization credentials, API permissions, JSON syntax, rendered identifiers, resource IDs, response body, and both Bloomreach and TRIFFT logs.

Q: What should I check when the webhook succeeds but no TRIFFT action occurs?

A: Verify that the rendered TRIFFT member ID is correct, the endpoint path and payload match the selected API operation, the API key has the required permission, and the Scenario did not send an empty or malformed dynamic value.