Partition Field Best Practices

Last Updated: 28/11/2024 Tags: personalization, personalisation, partitions, custom fields, organisation settings

Switch Version
V5
V4

Keeping your subscriber data clean and easily manageable is essential for your organization. There are a few ways to improve how to personalise your customers experience further. Here are some best practices and tips to keep your partition fields clean, easy to read and manageable:

Topic	Explanation
Use Custom Fields with Partitions	When personalizing content within your email, please ensure you're utilisting custom fields in tandem with partitions to ensure that subscribers are receiving the most accurate content. A basic template or tag can be seen as follows: `recipient.partition.custom.custom-field`.
When best to use Partitions	Partitions are mostly used to separate individual stores or franchisees, allowing more personalisation within Emails and Short message services (SMS). As such, Taguchi recommends using partitions to separate stores for easier targetting of customers via their local store.
Naming conventions	Generally you'll want to keep your partition fields easy to identify. Similar to how custom fields work, there's a basic syntax that needs to be followed. For example: `{%= recipient.partition.custom.STORE_NAME %}` or `{%= recipient.partition.custom.STORE_OPENING_HOURS %}` are good examples.

You may refer to these articles to find out How to create Partitions in Taguchi.
And How to make personalisations with the Personalisation Generator.

Support

Related articles

Need some help?

Taguchi Certified Training

API Version 4

Was this article helpful?

Thanks for your feedback!

Partition Field Best Practices