Bloomreach Implementation Partner: UAE, Saudi Arabia, Qatar, Kuwait

A Bloomreach implementation partner is the firm that sets up the Bloomreach products you've bought so they run on your own data and channels. In practice that means tracking, data imports, consent, automated campaigns, catalog feeds, search rules and content models. It ends with a handover your team can run.

In the UAE, Saudi Arabia (KSA), Qatar and Kuwait, the work also covers Arabic catalog data and right-to-left (RTL) templates. It covers WhatsApp and SMS too, and data handling under four different laws. This guide covers the deliverables per product, the phases and an indicative timeline, and the Gulf-specific work. It ends with how to evaluate a partner and what the handover should contain.

Still deciding who to hire? Start with our guide to choosing a Bloomreach partner agency. This one assumes you've bought, or are close to buying, and want to know how the project actually runs. It uses Bloomreach's current names: Marketing (formerly Engagement), Search (formerly Discovery) and Content.

What does a Bloomreach implementation partner deliver?

A working setup for each product you've licensed, plus the documents and training to run it. The scope differs a lot by product, so it helps to see the pieces side by side.

Product	Core implementation work	How you know it's done
Marketing	Tracking, customer IDs, imports, consent, automations, channels	Real events land on real profiles
Search	Catalog feed, search and category APIs, pixel, merchandising	Bloomreach's integration audit is passed
Content	Content model, channels, front-end integration, translations	Editors publish pages without developers
Data hub	One data integration shared across Bloomreach products	The same catalog shows in Marketing and Search

Data hub deserves a word. Bloomreach describes it as a single integration that makes your data available across its products. It's being rolled out in phases, and Bloomreach recommends it for new implementations "where available". Ask your partner early whether your project will use it, because it changes how catalogs and imports are built.

What does a Bloomreach Marketing implementation include?

Marketing is the customer data platform (CDP) and marketing automation app, and it's where many Gulf projects start. Bloomreach's own pricing page notes that most brands start with email. The work falls into four blocks.

Tracking and customer identity

The partner installs web tracking through Bloomreach's JavaScript SDK and, if you have apps, the mobile SDKs. The docs still call these the Exponea SDK, a leftover from the platform's origins. Then comes the most important design call: how customers are identified.

Bloomreach uses soft IDs, usually cookies, and hard IDs, usually an email address or your internal customer ID. Hard IDs are case-sensitive, so Bloomreach advises converting them to lowercase to avoid duplicate profiles. In the Gulf, phone numbers matter just as much. When an inbound WhatsApp message creates a profile, Bloomreach uses the phone format in your SMS settings, or a "00" format if none is set. Pick one format early, or the same customer can end up in two profiles.

Data imports and catalogs

Next, the partner imports customers, orders and product catalogs, and sets up recurring syncs. Watch the connector choice here. Bloomreach's Adobe Commerce (Magento) connector for Marketing is "not supported for new implementations as of January 1, 2026". New builds should use the Tracking API and imports into Data hub instead. If your store runs on Adobe Commerce, your Adobe Commerce agency will need to work with the Bloomreach partner on this.

Consent

Consent management is on by default for new Marketing projects. It stores each consent's category, status, source and history on the customer profile, and it can publish a self-service preference page. The partner's job is to turn your legal advice into categories, such as email, SMS and WhatsApp marketing or personalized ads. Each category then gets wired into every form and import.

Automations and channels

Bloomreach calls its automations scenarios. A first release usually includes a welcome series, abandoned cart and browse flows, and a post-purchase message. Channels then get connected one by one. Expect email through the visual or HTML builder, SMS and MMS, WhatsApp, on-site web layers, app push and ad audiences. Customer time zones can be mapped once in project settings so sends and quiet hours respect local time.

If you're comparing stacks, our explainer on Adobe omnichannel customer engagement shows how Adobe spreads the same jobs across several apps.

What does a Bloomreach Search implementation include?

Bloomreach documents Search integration as five phases: plan and design, connect the catalog, build the site experience and send events, tune and test, then launch. A partner should follow that structure, because Bloomreach's own team checks the work at the end.

• Catalog feed. Bloomreach says daily generation and delivery of the product feed "is a required ongoing step". Feeds go by API or SFTP, with optional delta feeds for faster updates.
• APIs and front end. The partner builds search results, autosuggest and category pages on Bloomreach's APIs, or uses a connector for Shopify or BigCommerce. A Magento extension exists, but Bloomreach labels it community-supported.
• Pixel. Page view and event pixels feed the learning. They can run in the browser, through a tag manager or server-side.
• Tuning. Synonyms, ranking rules, facets and merchandising rules get set and tested against real queries.
• Launch. About three weeks before go-live, a Bloomreach Technical Consultant runs a technical integration audit, and blockers must be fixed. After launch, Bloomreach's Launch Result Services usually deliver a before-and-after analysis or A/B test readout within 30 days.

What does a Bloomreach Content implementation include?

Content projects start with a choice between Content SaaS and self-hosted Content. Content SaaS is Bloomreach's hosted headless option. Its docs say environments run in a single public cloud region, "initially EU or US-East". Self-hosted Content can run on Bloomreach Cloud or in your own environment.

From there the partner models your document types and page components, sets up channels, and connects your front end. Bloomreach's developer docs point React and Next.js teams to its SPA SDK and Page Model API. For bilingual sites, Content supports localized channels, translation links between folders and page sync between translated channels. That's the backbone of an English and Arabic site that stays in step.

What are the phases of a Bloomreach implementation, and how long does it take?

Most Bloomreach projects follow the same arc, whatever the product mix. The ranges below are indicative, based on common market practice rather than Bloomreach figures. They assume one brand, one or two countries and reasonably clean data.

Phase	What happens	Indicative length
Discovery and design	Use cases, data map, ID rules, consent design, Arabic scope	2 to 4 weeks
Data and tracking	SDKs, pixel, imports, catalog feeds	3 to 6 weeks
Build	Automations, templates, search rules, content model	4 to 8 weeks
Testing	Data checks, Arabic and RTL review, consent tests	2 to 4 weeks
Launch and hypercare	Phased go-live, monitoring, fixes	2 to 4 weeks

Phases overlap, so a single-product launch usually takes less than the sum of the column. A few lead times are fixed by others, though. Bloomreach says WhatsApp onboarding "typically takes 3-4 weeks", because Meta must approve your business account and templates. The Search audit lands about three weeks before go-live.

Who does what during the project?

Three parties share the work, and most delays happen in the gaps between them:

• Your team: owns the data, legal sign-off, Arabic copy approval and the final go-live decision.
• The partner: designs and builds tracking, imports, automations, templates, search setup and content, then tests it all.
• Bloomreach: provisions the product, runs checks such as the Search integration audit, and supports you after launch.

Write these owners into the project plan, task by task, so nobody assumes someone else has it.

What moves the timeline and the cost?

• Products and countries. Each extra market adds catalogs, templates, consent rules and testing.
• Data quality. Messy customer IDs and product data are the most common cause of delay.
• Integrations. Enterprise resource planning (ERP), point of sale (POS) and loyalty systems each add design and testing.
• Arabic volume. Every Arabic template, product field and test case is extra work, and it grows with catalog size.
• Peak freezes. Launching inside Ramadan, Eid or a White Friday sale is risky, so plans usually work back from those dates.

Bloomreach's licence is a separate line from the partner's fees. Its pricing page says there's "No public rate card", and adds that smaller brands start at $60K a year (read 26 October 2026). Partner fees depend on the drivers above, so compare bids against the same written scope.

What Gulf-specific work does a Bloomreach implementation involve?

Three areas need extra design and testing in the Gulf: Arabic search, RTL templates and messaging channels.

Arabic catalog data and search

Bloomreach's Arabic support for Search comes with rules that shape the build:

• Arabic is "only available for API-based Data Delivery customers", so plan an API feed rather than file delivery.
• Attribute names stay in English, while attribute values can be in Arabic.
• Price and product ID fields only take western digits, unless you agree otherwise with Bloomreach's Technical Services team.
• Search removes diacritics, including Arabic short vowels, when it indexes and reads queries.
• Each language needs its own domain key and product feed, and with Data hub its own item collection.

So a bilingual store is, in effect, two catalogs. Build an Arabic test set from your own site search logs, and include common misspellings and any Latin-script Arabic your shoppers type.

RTL email and on-site templates

Marketing's email builders support one template version per language, and customers with no language set get the default. A new language version is a copy, so it won't pick up later changes to the default template. Bloomreach's docs don't describe an RTL switch in the visual builder, so ask Bloomreach how your Arabic versions should be built.

The HTML builder gives developers full control over the HTML and CSS, which is where direction and alignment can be coded. Whichever route you take, test Arabic templates in the mail apps your customers use. For self-hosted Content, rich text fields need CKEditor's "bidi" plugin enabled for RTL editing.

WhatsApp and SMS

Bloomreach documents both channels for Marketing. WhatsApp runs through Infobip or Sinch and is "only available in some Bloomreach packages", so confirm it's in your contract. You need an approved WhatsApp Business Account and approved templates from Meta. Free-form replies are allowed for 24 hours after a customer messages you first. For SMS, Bloomreach lists integrations with Infobip, Sinch and Twilio, plus double opt-in and two-way keyword replies. Sender registration rules differ by country, so check them with your messaging provider before launch.

How do data residency and consent work in the UAE, KSA, Qatar and Kuwait?

Start with where the data sits. Bloomreach says Marketing runs in Google data centers in three regions: EMEA (Belgium and London), North America and APAC (Sydney). None is in the Gulf. Files in Marketing's Asset manager are the exception, since Bloomreach doesn't guarantee their location and advises against storing anything sensitive there. If your legal team needs data to stay in-country, raise it with Bloomreach before signing.

Then map each country's rules to the build. This isn't legal advice, so confirm every point with counsel.

Country	Rule worth knowing	What the partner configures
UAE	The PDPL covers processors outside the UAE handling UAE residents' data, with set rules for cross-border transfers	A record of where each data set is stored and processed
Saudi Arabia (KSA)	A separate regulation governs transfers outside the Kingdom, and sensitive data can't be used for marketing	Sensitive fields kept out of segments and campaigns
Qatar	Article 22 requires prior consent for electronic direct marketing	Sender identity, a "direct marketing" label and an opt-out address in every message
Kuwait	CITRA says sharing personal data with third parties needs the person's knowledge and permission	Consent checks before ad audiences or exports go to partners

Qatar's rule is the most hands-on for a marketing build, because it reaches into every template. Saudi Arabia's ban on marketing with sensitive data holds "even with an individual's consent", according to SDAIA's guide. Kuwait's regulation should be checked on CITRA's site for its current version.

How do you evaluate a Bloomreach implementation partner?

Ask for artifacts, not adjectives. A partner that has done Gulf builds can show you real work with client names removed.

• A tracking plan with events, properties and customer ID rules.
• A Search feed spec that shows how Arabic values and western-digit prices are handled.
• An Arabic search test plan built from real queries.
• A consent map for each country you serve.
• An Arabic email template they've shipped, opened in two or three mail apps.
• A plan for Bloomreach's integration audit and who fixes blockers.

Red flags are just as telling. Be wary of a partner that proposes the legacy Adobe Commerce connector for a new Marketing build. The same goes for promises of Arabic search on file-based feeds, or a test team with no Arabic speaker.

For a starting point, Bloomreach's partner records list a few firms with Dubai offices, including Double T Agency and SQLI (alphabetical, not a ranking). Double T's record tags implementation and omnichannel orchestration among its capabilities. SQLI's tags commerce and search and merchandising. Neither record names Saudi Arabia, Qatar or Kuwait, so ask about delivery there. Our guide to choosing a Bloomreach partner agency explains what these listings do and don't prove.

If Bloomreach sits inside a wider Adobe or Google program, our partner finder covers firms for that side. The partner comparison tool lines finalists up by tier and delivery region, and the Partner Advisor turns a plain-language brief into a shortlist.

What should the handover include?

A good handover leaves your team able to run, fix and extend the setup without the partner. Put these items in the contract, not in a goodwill email:

• Documentation: tracking plan, data dictionary, ID rules, consent map, feed spec and schedule, and merchandising rules.
• An inventory: every automation, template and search rule, each with an owner and its Arabic version.
• A runbook: what to do when an import fails, a feed is late or WhatsApp templates are rejected.
• Ownership: your Bloomreach project, Meta business account, sender IDs and API keys held in your company's name.
• Training: Bloomreach Academy courses for the people who'll run each product.
• A Bloomreach handoff: for Search, Bloomreach moves the account to its Support team after launch, and your Account Manager becomes the main contact.

Agree a hypercare window after launch, then decide whether support moves in-house or to a retainer.

What to do next

Here's a short checklist before you sign a Bloomreach implementation partner:

• Confirm which products, channels and countries are in your contract, including WhatsApp.
• Decide whether the build will use Data hub.
• Ask Bloomreach where your data will be hosted, and check that with counsel for each country.
• Collect your top Arabic and English search queries and your consent wording.
• Ask shortlisted partners for the six artifacts above and a phase plan with named people.
• Work back from Ramadan, Eid and White Friday to set a realistic launch date.

To turn this checklist into a brief, adapt the deliverable and handover questions in our partner RFP builder, which was designed for Adobe and Google work.