Klaviyo
automation.

Unsubscribe a person from Klaviyo marketing (email and/or SMS). NOTE: Despite the historical verb name (`cancel_marketing`), this action is for cancelling marketing *to a person* (unsubscribe), not cancelling a campaign send. WORKFLOW: 1. Identify the person by email and/or phone and/or profile_id 2. Submit a bulk-unsubscribe job to Klaviyo 3. Klaviyo processes the unsubscribe asynchronously CRITICAL REQUIREMENTS: - Provide at least one identifier: email, phone_number, or profile_id - If you provide list_id, the unsubscribe is scoped to that list - WARNING: If you provide list_id and the profile is NOT in that list, Klaviyo may globally unsubscribe them USE CASES: - Customer asks to stop receiving marketing emails - Customer asks to stop receiving marketing SMS - Compliance / preference center sync LIMITATIONS: - This does not cancel a campaign send already in progress - Some unsubscribe operations are processed asynchronously by Klaviyo

WORKFLOW: 1. Identify profile by profile_id, email, or phone 2. Send deletion request to Klaviyo API 3. Profile and all associated data are permanently deleted CRITICAL REQUIREMENTS: - This is PERMANENT and IRREVERSIBLE - Deletes profile, events, relationships, and all associated data - Cannot be undone - use with extreme caution - Requires at least one identifier: profile_id, email, or phone USE CASES: - GDPR data deletion requests - Privacy compliance (CCPA, GDPR) - Customer requests to be removed - Cleaning up test/duplicate profiles - Data retention policy enforcement DANGER: - PERMANENT DELETION - cannot be recovered - Deletes all historical data for the profile - Affects analytics and reporting - Consider exporting data before deletion if needed IDENTIFIER PRIORITY: - If profile_id provided, uses it directly (fastest) - If email provided, looks up profile by email first - If phone provided, looks up profile by phone first - Must provide at least one identifier

WORKFLOW: 1. Submit unsubscribe request via bulk job endpoint (required by Klaviyo API) 2. Profile is globally unsubscribed from all marketing 3. Consent status changes to "Unsubscribed" 4. Profile will no longer receive marketing emails or SMS CRITICAL REQUIREMENTS: - This is a GLOBAL unsubscribe - affects ALL lists - Profile will no longer receive ANY marketing communications - Profile data is retained (not deleted) for compliance/analytics - To delete data entirely, use klaviyo:delete_data for GDPR requests USE CASES: - Customer requests "unsubscribe me" via support - Compliance with unsubscribe requests - Managing marketing consent - CAN-SPAM Act compliance IMPORTANT NOTES: - Profile remains in system but won't receive marketing - Can be manually resubscribed later if customer requests - Does NOT delete profile data (use delete_data for that) - Affects both email and SMS marketing channels