Marketing Cloud and Data 360

Marketing Cloud from Salesforce focuses on deeply understanding your customers and tailoring messages to engage with them according to their preferences. It offers marketing automation for both B2C and B2B, along with audience segmentation and precise targeting and retargeting capabilities.

Arcsen implements Marketing Cloud and Data 360 (formerly Data Cloud) for organizations in the Gulf and Egypt: one customer profile from CRM, web and ERP data, and campaigns in Arabic and English on email, SMS and WhatsApp. Clean, consented data decides whether a message reaches the right person, in their language.

What we build

Campaigns are the easy part, the data under them is the work.

One profile in Data 360

We bring CRM, web, app, ERP and event data into Data 360 and agree identity rules with your teams: normalized mobile and email matches, plus fuzzy name matching for cross-cultural spellings. Source records stay untouched.

Arabic and English, as pairs

We build email, SMS and WhatsApp templates as Arabic and English pairs, and check right-to-left layouts on real devices and email clients. Language preference sits on the profile, so each customer gets one version in their chosen language.

WhatsApp and SMS, by local rules

We connect the WhatsApp Business Account and submit template messages for Meta’s approval. For UAE SMS, promotional sender IDs start with “AD-”, consent is registered before carriers deliver, and promotional sends stay between 7 AM and 9 PM UAE time.

Consent you can prove

In Marketing Cloud Next, consent sits per channel on each contact point, so a customer can accept WhatsApp and decline email. We record when, where and in which language each opt-in was given, and add double opt-in where needed.

ERP and dealer data in the profile

We bring purchase, contract and vehicle data from ERPs and dealer systems into the profile, so segments know what a customer owns. Our work for Soudah Development connects to Oracle Fusion, and for Alfardan and Al Jazirah Vehicles to the Keyloop DMS.

Brands kept apart

Data 360 data spaces split data, metadata and processes by brand, region or department. Marketing Cloud Engagement business units do the same for content and subscribers. We design both around how your group reports.

Client work

Who we build it for, by name.

How we deliver

Data first, then campaigns in releases.

01

Audit the data

We list every source of customer data, from CRM and web to ERP, dealer systems and event lists, and measure duplicates, gaps and consent coverage. Identity rules come from that audit.

02

Agree consent and language

Channels, purposes and opt-in wording are agreed in Arabic and English with your legal team, along with how proof of consent is kept. Native speakers review each template pair before build.

03

Release in stages

The first release covers the unified profile, core segments and one or two channels. Further sources, channels and automated programmes follow, each tested against real volumes and live consent.

04

Run and improve

After go-live, our managed services team watches data streams, deliverability and consent errors, and tunes segments with your marketers. Every change is logged, so you can see what ran and what failed.

Questions we get

Asked by every buyer, answered straight.

Which Marketing Cloud edition should we buy?

For new customers, Salesforce’s starting point is Marketing Cloud Next, in Growth or Advanced edition. It runs on the Salesforce Platform with Data 360 and needs Salesforce Enterprise or Unlimited edition. Teams on Marketing Cloud Engagement or Account Engagement can stay, or renew into Engagement+ or Account Engagement+. We size the choice on your volumes.

Does it work in Arabic?

Customers can receive emails, SMS and WhatsApp messages entirely in Arabic. For your team, Marketing Cloud Next and Data 360 list Arabic as an interface language. Marketing Cloud Engagement and Account Engagement do not, so their users work in English or another supported language.

How do you handle consent and opt-outs?

Your legal team sets the policy and we implement it. Marketing Cloud Next checks consent against a communication subscription before promotional sends, and Data 360 applies consent preferences to activations. UAE SMS adds carrier-registered consent and opt-outs through short code 7726.

Can Data 360 use our SAP or Oracle data?

Yes. Data 360 has a generally available SAP HANA connector, with batch ingest or zero copy. For SAP S/4HANA, Oracle Fusion and other ERPs, we bring data in through MuleSoft or the Ingestion API. Before mapping, we agree with finance and IT which fields marketing may use.

Find the data problems first, before they reach every segment.

Start with a free Salesforce health check

Or talk to the team. See also: Real estate clients · Retail and distribution clients · Automotive clients.