client_user_agent, action_source, and event_source_url parameters, while non-web events require only action_source. These parameters contribute to improving the quality of events used for ad delivery and may improve campaign performance.action_source parameter is accurate to the best of your knowledge.em: Email — Hashing requiredph: Phone Number — Hashing requiredfn: First Name — Hashing requiredln: Last Name — Hashing requiredge: Gender — Hashing requireddb: Date of Birth — Hashing requiredct: City — Hashing requiredst: State — Hashing requiredzp: Zip Code — Hashing requiredcountry: Country — Hashing requiredexternal_id: External ID — Hashing recommendedclient_ip_address: Client IP Address — Do not hashclient_user_agent: Client User Agent — Do not hashfbc: Click ID — Do not hashfbp: Browser ID — Do not hashsubscription_id: Subscription ID — Do not hashfb_login_id: Facebook Login ID — Do not hashlead_id: Lead ID — Do not hashanon_id: Install ID — Do not hash (Note: This parameter is for app events only)madid: Mobile Advertiser ID — Do not hash (Note: This parameter is for app events only)page_id: Page ID — Do not hashpage_scoped_user_id: Page scoped user ID — Do not hashctwa_clid: Click to WhatsApp ID — Do not hashig_account_id: IG account ID — Do not hashig_sid: Click to Instagram ID — Do not hashevent_nameevent_timeuser_datacustom_dataevent_source_urlopt_outevent_idaction_sourcedata_processing_optionsdata_processing_options_countrydata_processing_options_statereferrer_urlcustomer_segmentationadvertiser_tracking_enabledapplication_tracking_enabledextinfocampaign_idsinstall_referrerinstaller_packageurl_schemeswindows_attribution_idanon_idmadidvendor_idfbp and fbc Parameters