ZenWeb - Blog - Meta Conversions API and PDPA: Sending Customer Data Safely

Meta Conversions API and PDPA: Sending Customer Data Safely

November 2, 2026

Share this post:

Meta Conversions API and PDPA: Sending Customer Data Safely
TL;DR: Meta’s Conversions API sends customer details such as emails and phone numbers from your server to Meta. Hashing scrambles them, but they are still used to identify people, so treat them as personal data under the PDPA. Tell customers in your notice, send only the fields you need, keep sensitive data out, secure the server and access keys, and agree processor duties in writing with whoever runs the setup.

Many Malaysian advertisers switched on Meta’s Conversions API (CAPI) because a plugin or agency said it would “fix tracking”. It often does. Few owners ask what customer data now leaves their website, or whether their privacy notice says so.

This guide answers Conversions API PDPA questions from the advertiser’s side: which fields go to Meta, whether hashing changes the legal position, which principles apply, and a checklist. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients that sets up Meta tracking every week. We handle the tracking and website side; we are not a law firm. Rules are stated as at October 2026.

This post is general information, not legal advice. Please confirm how the PDPA applies to your own setup with a licensed lawyer.

Not sure what your Meta setup is sending?

We audit Pixel and Conversions API events field by field, then trim them to what your campaigns actually need. See our Meta Ads services →

If the Pixel and Conversions API are new to you, this short explainer shows how the two work together before we get to the privacy side.

Meta Pixel and Conversions API Explained

Source video: Rihards Zeiļa on YouTube. A general tracking explainer; it does not cover Malaysian privacy law.

1. What Customer Data Does the Conversions API Send to Meta?

Quick Answer: Each server event can carry “customer information parameters”: email, phone, name, date of birth, gender, city, state, postcode and country, plus IP address, browser details and Meta’s click and browser IDs. Contact fields must be SHA-256 hashed before sending; IP address and user agent must not be hashed.

The Pixel runs in the visitor’s browser. The Conversions API runs from your server, plugin or gateway, so it can send data the browser never sees, such as a CRM email. That improves matching, and it is why a privacy check matters.

Common Conversions API customer fields and how the PDPA is likely to view them, as at October 2026
Data table listing common Meta Conversions API customer information parameters, whether Meta requires them to be hashed, and how Malaysia’s PDPA is likely to treat each one.
Field (Meta parameter)Meta hashing ruleLikely PDPA view
Email (em), phone (ph)Must be SHA-256 hashedPersonal data; used to match a person
Name (fn, ln), date of birth (db), gender (ge)Must be hashedPersonal data; often not needed
City, state, postcode, countryMust be hashedPersonal data when combined with other fields
External ID (your customer ID)Hashing recommendedPersonal data; links to your CRM record
IP address, user agentMust not be hashedTreat as personal data; sent in clear text
Click ID (fbc), browser ID (fbp), lead IDMust not be hashedOnline identifiers tied to a person’s activity

Source: Meta customer information parameters; PDPA column is ZenWeb’s reading of Act 709, not a regulator ruling. As at October 2026. Licence.

Most setups do not need every field, even if a plugin switches them all on. For the technical setup itself, see our Meta Pixel and Conversions API setup guide.

Key takeaway: Before any legal question, list exactly which fields your server sends. You cannot write an honest notice for data you have not mapped.

2. Is Hashed Data Still Personal Data Under the PDPA?

Quick Answer: Treat it as personal data. Hashing turns an email into a fixed code, but the same email always gives the same code, and Meta uses it to match a real account. The PDPA covers data that identifies a person directly or indirectly, so hashing is a security step, not an exemption.

Many owners assume “hashed means anonymous”. It does not. Hashing works more like a lock than deletion:

  • It protects data in transit. A hashed email is useless to someone who intercepts it without the original list.
  • It still identifies. Anyone holding the same email can hash it and find the match. That is exactly what Meta does.
  • It does not remove your duties. Section 2 of the Personal Data Protection Act 2010 covers information that identifies a person directly or indirectly, and matching data does exactly that.

Meta’s Business Tools Terms say contact information is processed only to match it to user IDs and is deleted after the match. That limits Meta’s use, but you still disclosed the data. As at October 2026, we found no Commissioner guideline on hashed advertising data, so take the cautious view for now.

Key takeaway: Hash every contact field, because Meta requires it and it reduces risk. Then plan your notice and security as if the data were unhashed.

3. Which PDPA Principles Apply to a Conversions API Setup?

Quick Answer: All seven principles touch it, but four matter most: Notice and Choice (tell people), Disclosure (Meta is a third party you name), Security (protect the server and tokens) and Retention (stop sending stale data). The 2024 amendments add breach notification, processor duties, DPO triggers and new cross-border rules.

The Personal Data Protection (Amendment) Act 2024 (Act A1727) raised the maximum penalty for breaching a principle to RM1,000,000, three years’ jail, or both. Here is how each rule affects a Conversions API PDPA review.

PDPA rules grouped by what they mean for a Meta Conversions API setup
Grouped table mapping Malaysian PDPA principles and 2024 amendment rules to practical actions for an advertiser using Meta’s Conversions API.
GroupPDPA ruleWhat it means for CAPI
Before sendingGeneral (s.6)Send only what the ad purpose needs
Notice and Choice (s.7)Say in your notice that data goes to advertising partners
While sendingDisclosure (s.8)Name Meta’s class of recipient in the notice
Security (s.9)Hash, use HTTPS, guard the access token
Over timeRetention and Integrity (s.10, s.11)Do not re-upload old or wrong CRM records
Access (s.12) and portabilityKnow what you sent if a customer asks
2024 amendmentsCross-border transfer (s.129)Meta processes data outside Malaysia
Breach notification (s.12B)A leaked token or server can be a notifiable breach
Data protection officerBehavioural advertising can trigger the DPO duty

Source: ZenWeb mapping of Act 709 and Act A1727 to a Meta Conversions API setup. As at October 2026. Licence.

Two rules catch advertisers off guard. The DPO guideline treats regular tracking for behavioural advertising as systematic monitoring; see who must appoint a data protection officer. And because Meta’s servers sit overseas, read our guide to cross-border data transfer under PDPA, which covers the Commissioner’s cross-border transfer guideline.

Key takeaway: Conversions API PDPA compliance is not one rule. It is notice before sending, security while sending, and discipline over what you keep sending.

4. Which Fields Should You Send, and Which Should You Leave Out?

Quick Answer: Start with email, phone, click ID, browser ID, IP and user agent, which do most of the matching. Add name or postcode only if they clearly help. Never send health, financial or other sensitive details, data about children under 13, or free-text form answers. Meta’s terms forbid these too.

This illustrative scenario weighs each field’s matching value against its privacy weight for a typical SME lead form.

Illustrative scenario: matching value vs privacy weight by field (score out of 10)
Bar chart table scoring, in an illustrative scenario, the matching value and the privacy weight of six Conversions API field groups, with a send or skip suggestion.
Field groupMatching valuePrivacy weightSuggestion
Email + phone (hashed)9

6

Send, with notice
Click ID + browser ID8

3

Send
IP + user agent6

4

Send
Name + postcode (hashed)4

5

Only if clearly useful
Date of birth + gender2

7

Usually skip
Sensitive or free-text answers0

10

Never send

Source: Illustrative scenario by ZenWeb. Scores are judgement-based assumptions to show the trade-off, not measured Event Match Quality data or a legal standard. As at October 2026. Licence.

Two checks keep the payload lean:

  • Check custom data, not just user data. Event names and “content” fields can leak details, such as a product name that reveals a sensitive purchase.
  • Watch the URL. Form answers in page URLs travel with every event, so fix the form itself.

Section 40 of the PDPA needs explicit consent for sensitive personal data, and Act A1727 added biometric data to that list. If a lean setup leaves gaps in reporting, our Conversions API troubleshooting checklist covers fixes that do not need more personal data.

Key takeaway: Email, phone and Meta’s own IDs do most of the work. Every extra field adds privacy weight for a small gain, so add fields only when you can explain why.

5. What Should Your Privacy Notice Say About Conversions API?

Quick Answer: Say that you share contact and activity data, in protected form, with advertising partners such as Meta to measure ads and show relevant ads, and that data may be processed outside Malaysia. Put it in English and Bahasa Malaysia, link it from every form, and offer a way to opt out.

Meta’s Business Tools Terms also require a clear, prominent notice on every website using its tools, plus any consent local law requires. Illustrative wording for a form or checkout page:

English: We share your email, phone number and website activity, in protected (hashed) form, with advertising partners such as Meta to measure our ads and show you relevant offers. This data may be processed outside Malaysia. To opt out, email privacy@yourcompany.example. See our Privacy Notice.

Bahasa Malaysia: Kami berkongsi e-mel, nombor telefon dan aktiviti laman web anda, dalam bentuk dilindungi (dicincang), dengan rakan pengiklanan seperti Meta untuk mengukur iklan kami dan menunjukkan tawaran yang berkaitan. Data ini mungkin diproses di luar Malaysia. Untuk menarik diri, e-mel privacy@yourcompany.example. Lihat Notis Privasi kami.

Fold this into your existing form notice; our guide to contact form PDPA notice wording shows the layout. For lead forms inside Facebook, see Facebook lead ads and PDPA. Cookies are covered in do you need a PDPA cookie banner, and Google Analytics in Consent Mode and PDPA.

Key takeaway: Server-side tracking is invisible to visitors, so the notice is the only place they learn about it. Name the purpose, the recipient class and the overseas processing.

Want tracking that is accurate and explainable?

We set up the Pixel, Conversions API and form notices together, so what you send always matches what you tell customers. Book a Meta tracking review →


6. What About CRM Uploads and Offline Conversions?

Quick Answer: Sending lead status or in-store sales from your CRM through the Conversions API uses older data for a new purpose: ad measurement. That purpose must be in your notice. Send only records still within your retention period, and remove people who opted out or asked for deletion.

Offline and CRM events are where SME setups drift most, because a sales team uploading a year of WhatsApp leads is a different flow from website tracking. Before each upload:

Members’ purchase histories need extra care; see loyalty programme data under PDPA. If a customer asks for their data under the new portability right, you should be able to say what you sent; see data portability under PDPA. For the setup itself, see our Meta offline conversions service.

Key takeaway: Filter every CRM upload by source, age, opt-out and open requests. A clean upload list protects both compliance and match quality.

7. Who Is Responsible: You, Your Agency or Meta?

Quick Answer: You, the advertiser, are the data controller: you decide to collect and send the data. An agency, developer or gateway host acting on your instructions is a data processor, and since Act A1727 processors carry their own security duty. Meta processes matching data under its own terms.

Clear roles stop the “I thought the agency handled that” problem. Most Malaysian SME setups split like this:

Typical PDPA responsibilities in an SME Conversions API setup
Data table showing the PDPA role and main duties of the advertiser, the agency or developer, the server or gateway host, and Meta in a typical Conversions API setup.
PartyLikely roleMain duties
Advertiser (your business)Data controllerNotice, field choices, retention, requests, breach reports
Agency or developerData processorFollow instructions, secure tokens, report incidents fast
Server or gateway hostData processorServer security, access logs, location of servers
MetaRecipient under its Business Tools TermsMatching, then deleting contact data; its own policies

Source: ZenWeb reading of Act 709 as amended by Act A1727, and Meta’s Business Tools Terms. Roles depend on your contracts; confirm with a lawyer. As at October 2026. Licence.

Put processor duties in writing, including who holds the access token and how fast incidents are reported. Our guide to your agency’s data processor duties under PDPA lists the clauses. If a token or server leaks, the data breach notification guideline applies; see data breach notification in Malaysia. AI tools raise similar issues; see AI and PDPA for Malaysian marketers.

Key takeaway: Outsourcing the setup does not outsource the responsibility. Keep ownership of the Meta Business account and the access token, and grant agency access through roles.

8. Conversions API PDPA Checklist: 8 Steps

Quick Answer: Map the fields, trim them, block sensitive data, hash and secure, update the bilingual notice, filter CRM uploads, sign processor terms, and review twice a year. Most SME setups can complete this in a week, with the notice and processor terms taking longest.

Run this Conversions API PDPA review for every plugin, gateway and CRM connection that feeds Meta:

  1. Map the payload. Use Events Manager’s test events to see every field each event sends.
  2. Trim the fields. Keep email, phone, Meta IDs, IP and user agent; justify anything else.
  3. Block sensitive data. Remove health, financial, children’s and free-text data, including from URLs and product names.
  4. Hash and secure. Confirm SHA-256 hashing, HTTPS and that the access token is not stored in public code.
  5. Update the notice. Add the advertising partner, overseas processing and opt-out line in both languages.
  6. Filter CRM uploads. Exclude old records, opt-outs, bought lists and open deletion requests.
  7. Sign processor terms. Agree token custody, security and incident reporting with your agency and host.
  8. Review twice a year. Plugins update, fields reappear; re-check after every major site change.

For the full set of marketing rules beyond tracking, use our PDPA compliance checklist for Malaysian marketers. For why server-side tracking matters in the first place, see server-side tracking explained.

Key takeaway: The setup is not finished when events show as “received”. It is finished when you can explain every field to a customer.

9. Conclusion: Send Less, Say More

The PDPA does not stop Malaysian advertisers using the Conversions API. As at October 2026, a safe Conversions API PDPA setup has:

  • A lean payload of hashed contact fields and Meta IDs, with no sensitive data.
  • A bilingual notice naming advertising partners and overseas processing.
  • Clean CRM uploads that respect retention, opt-outs and requests.
  • Written processor terms and a token you control.

Where a rule is still unclear, such as the status of hashed data, take the cautious reading until new guidance appears. For tracking set up properly from day one, talk to our Meta Ads team.


10. Frequently Asked Questions

1. Is the Meta Conversions API legal in Malaysia?

Yes. Nothing in the PDPA bans it, but Conversions API PDPA compliance still means giving notice, sending only what you need, keeping it secure and handling overseas transfer properly.

2. Does hashing make Conversions API data anonymous?

No. A hashed email still matches one person, which is how Meta uses it. Treat hashed fields as personal data and hash them anyway, because Meta requires it and it improves security.

3. Do I need consent before sending data through the Conversions API?

The PDPA’s general rule is consent with proper notice, and sensitive data needs explicit consent. Meta’s terms also require any consent your local law demands. Confirm the right approach for your business with a lawyer.

4. Can I upload my whole customer list to Meta?

Only records collected under a notice covering advertising use, within your retention period and not opted out. Leave out bought lists and stale records.

5. Can ZenWeb make our Meta tracking PDPA-friendly?

Yes, on the technical side. We map and trim your events, secure the setup and align your form notices. Final legal wording should be checked by a licensed lawyer.

Cite this page: ZenWeb (2026). Meta Conversions API and PDPA: Sending Customer Data Safely. https://zenweb.my/blog/conversions-api-pdpa/

You may quote our data with this credit and a link. See our Terms of Use.

Get Meta tracking you can stand behind

Talk to ZenWeb about a Pixel and Conversions API setup that measures your ads accurately and sends only what your notice covers. We handle the tracking; your lawyer confirms the legal wording.

Book a free consultation →

Table of Contents
Table of Contents

Get A Free Proposal

Complete the form and our team will contact you to discuss your goals. Let’s grow your business.