Set Up Account-Specific Redirects for ABM Pages

From a CTA, you can direct known page visitors to specific URLs and unknown visitors to a default destination by creating a Custom field for ABM Account.

To create a Custom URL for an ABM Account, follow the steps below: 

1. From the Left Nav Menu, go to Setup > Field Management > Select Account from the drop-down to access ABM Account Fields.  Click New Custom Field.
    
2. In the Add Custom Field box, enter the Name of the Field (Example: Account CTA), and the Code is generated automatically. Note: Learn more about adding a Custom Field here. 
   
   
3. From the Field Type drop-down, select Textbox, and from the Data Type drop-down, select String. Enter a default value in the Default Value field (optional). Click Save. 

Adding the new Custom Field to an ABM Account:

1. From the Left Nav menu, click  ABM >Accounts. 
2. On the Accounts page, click the Configure tab. 
3. Scroll to the Custom Fields section. Add the Account-specific URL and click on Update.
   
   
4. Next, navigate to ABM > Pages and select the page where you want to add the CTA.
    
5. Click the Tokens button located at the top-right corner of the page.  
   You will see the added token field on the Tokens pop-up. Enter a default destination in the field. Then copy it and close the pop-up window.
    
6. On the ABM Page > CTA, add the Button Text and the copied Token URL. Click Publish to apply and make the changes effective.
   

   
   Functionality in Realtime:

• When a user visits the page and belongs to the targeted account, the Call-to-Action (CTA) will take them to the account-specific destination URL configured for that account. This ensures a personalized and relevant user experience based on account-level targeting.
  
  For Example, the ACME account has a custom field Account CTA configured with the URL https://resources.hushly.com, while the ABM CTA token is set to https://hushly.com/demo-request. When Visitor A, who is associated with the ACME account, clicks the CTA on the ABM page in real time, they are redirected to the resources page (https://resources.hushly.com) based on the account-specific configuration.
  
  

• However, if the user comes from a different targeted account, the CTA will redirect them to the default destination URL instead. This fallback behavior ensures all users have a destination to land on, even if they do not match a specific account configuration.
  
  For Example, Visitor B, who belongs to a different targeted account without a specific Account CTA URL configured, visits the same ABM page. When they click the CTA, they are redirected to the default URL set in the ABM page configuration, in this case, https://hushly.com/demo-request.