How to Customize Your Content Strategy Fields

Modified on Tue, 18 Jun at 2:18 PM

DivvyHQ comes equipped with a set of native fields (metadata) that are intended to help customers define their content strategy and aid in strategic reporting. And while we encourage customers to utilize those fields based on their original intent, we also recognize that one or more of our content strategy fields may not be relevant to your use case. Or you'd like to re-label or customize one or more fields to store unique data for tagging purposes.

 

Thus we've introduced a customization feature to enable Account Admins to repurpose (rename) individual content strategy fields.


The Divvy Details

We've made it easy for you to customize your content strategy fields so that they match your unique use case. Below is a step-by-step guide to walk through the process.


IMPORTANT NOTE: Any field customization will be applied across your entire account, so if you have multiple teams/departments using your Divvy account, you may want to confer with them to ensure that any field you rename will be applicable for each team.

 


Step 1: If you are a Global Admin and Billing Admin for your account, click your name in the top right and select Account Admin.

 

account-admin-link.png















Step 2: Click the Account Customization tab.


account-customization-tab.png



Step 3: Click the Rename (edit) icon next to whichever Content Strategy field you wish to change. After you save it, you will see the change reflected in the Content Strategy section back in the Calendar Admin area.

 

Step 4: Within the Account Admin > Calendar Admin > Content Strategy tab, you can now input the applicable metadata/tags that align with your repurposed use case.  

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article