Normalize Phone Number

Google libphonenumber behind OAuth2 client credentials, with memory-only processing.

Marketo setup

1. Ask the service operator to provision an OAuth client for your Marketo instance and approve its exact HTTPS callback URL or a narrow path prefix. Each instance uses separate credentials.
2. In Marketo Admin → Service Providers → Add New Service, enter https://libphonenumber.app.vieten.cloud/openapi.json.
3. Enter your client ID and client secret. Map the outgoing phone field. Map incoming formatted values to dedicated fields initially. Overwriting the original phone field is optional.
4. Use Normalize Phone Number in a Smart Campaign. Select the output format and the two-letter default country code for national numbers.
5. Test with fictional example numbers before processing customer data. Monitor Marketo service errors and callback warnings.

Privacy and reliability

Phone numbers are processed transiently in RAM and returned only to the requesting API client or its approved Marketo callback. There is no database, disk queue, analytics, or request logging. Phone values are excluded from activity attributes. Marketo still stores its own source fields, mapped results, and change history.

Accepted work is held only in memory. Restarts, crashes or exhausted callback retries can lose a batch. Check Marketo outcomes and rerun affected records. Tokens expire after five minutes and restart invalidates all tokens.

Number validity reflects published numbering plans. It does not prove ownership, reachability, consent, or a lawful basis for marketing. The operator must establish legal basis, processor agreements, access controls and retention rules in Marketo.

Support: contact the operator who supplied your OAuth credentials. The service never needs your Marketo REST client secret.