Custom Parameters FAQ

Q: How do I use these parameters to personalize a Push Notification or News article?

A: You can insert Personalization Tokens directly into your content using the format {{member.attribute_key}}. When the message is sent, the system automatically replaces this placeholder with the specific value stored in that member's profile, such as their first name or their favorite store location.

Q: Where can I control if a member can see or edit their own custom parameters?

A: Visibility is managed under Settings > Custom Parameters. For each parameter, you can toggle Public Visibility. If enabled, the attribute becomes visible in the member's profile within the Mobile App or Web Portal. You can also decide if the member has permission to edit that information themselves.

Q: What happens if a member is missing the data for a parameter used in a message?

A: If a message uses a token like {{member.first_name}} but the field is empty for a specific recipient, the system will not insert anything and the placeholder for that custom parameter will be left blank.

Q: Why were some custom parameters not updated even though the API returned a 200 response?

A: A 200 response confirms that the request was processed successfully, but it does not necessarily mean that every custom parameter was updated. If a custom parameter contains an incorrect or non-existent slug, its value may not be saved.

This commonly happens with custom parameters nested inside a Group. The group slug must be used only as the parent object. Do not include the group slug again in the slugs of its nested parameters.

For example, consider a group with the following configuration:

Group slug: Children
Nested parameter slugs: Name and BirthDate

The correct payload is:

{
  "hasChildren": "true",
  "Children": [
    {
      "Name": "Matteo",
      "BirthDate": "2024-10-31"
    }
  ]
}

The following payload is incorrect:

{
  "hasChildren": "true",
  "Children": [
    {
      "Children_Name": "Matteo",
      "Children_BirthDate": "2024-10-31"
    }
  ]
}

In the incorrect example, Children is already defined as the parent group. The nested fields must therefore use only their own slugs: Name and BirthDate.

If some values are not updated, verify that all slugs exactly match the custom parameter configuration in your project, including capitalization.