Loading

Marketing Cloud Personalization | HTTP 403 Forbidden Error During Mobile SDK Initialization

Date de publication: May 11, 2026
Description
This article explains the causes and solutions for HTTP 403 Forbidden errors that occur during Marketing Cloud Personalization iOS/Android SDK initialization. The primary cause is a strict string mismatch in the Account name or Dataset name, which prevents Event Stream logging and all other SDK features from functioning.
Résolution

When initializing the Marketing Cloud Personalization Android/iOS SDK, the initialization may fail with an HTTP 403 Forbidden error.
As a result, events are not recorded in Event Stream and other features become unavailable. Because no compile errors are thrown, check the app development console to identify the issue.

[Error Example]

EVG Error [Evergage.m:541] Config: update error, keeping existing config. Send request failed, status code 403 Account ["Your Account Name"] is not entitled to make requests in this region [XXX] Check the format of the request and retry at a later time.
 

[Primary Cause]

・Account name or Dataset name is incorrect (case mismatch or wrong combination)
A 403 error occurs when the Account name or Dataset name specified in the SDK initialization code is incorrect. These values are case-sensitive and must exactly match the strings shown in the MC Personalication admin console. ( ENGAGE=> Engage)

In addition, the Account name and Dataset name must be a valid combination. Specifying a Dataset that belongs to a different Account will also result in a 403 error. Verify that both values belong to the same Account.

[How to Verify]

・Account name
In the Personalization UI, click the Gear icon in the left menu (Gears → Gears). Copy the Account name exactly as it appears in the URL (preserving case).
Note: The Dataset name shown in the URL appears in all lowercase and may not reflect the correct casing. Use the method below to verify the Dataset name instead.

Example: In https://demo.us-1.evergage.com/..., the value demo is the Account Name to specify here.
Since it is often a random string of characters, avoid typing it manually and always copy it directly from the URL.
 
・Dataset name
Click [Manage Datasets] to open the dataset list, then copy the Dataset name from there. Do not rely on the URL — viewing without clicking may display all-uppercase names (e.g., use Engage, not ENGAGE). Always click through to confirm the exact casing.
 
Example:
  • [NG] ENGAGE, engage — displayed in the URL (all-uppercase or all-lowercase)
  • [OK] Engage — the actual registered Dataset name shown after clicking through

Reference: How to Check Your Dataset Name

 

[Other Causes]

If the Account name and Dataset name are correct, also verify the following:

  • Bundle ID (iOS): Confirm that the app's Bundle ID matches the value registered in the Personalization admin console.
  • URL Scheme (Android): Confirm that the app's URL Scheme is correctly configured and registered.
Numéro d’article de la base de connaissances

005317469

 
Chargement
Salesforce Help | Article