How to use a custom header instead of MSISDN in a Target Group file

For SMS and MMS channels Webex Campaign requires MSISDN as a header in the target group file. You can also configure a custom header such as 'CTN' or 'Cellphone' to be used instead of MSISDN.

📘

This is a tenant-specific feature. If you would like to enable this feature for your tenant, please contact your Cisco Webex representative or the Webex CPaaS Tech Support team. You have to provide the name of the custom header that you would like to use within your target group files, instead of the default ‘MSISDN’ header

Usage notes:

a) This feature is only applicable to SMS and MMS channels.
b) At the time of Target group (TG) creation, Webex Campaign will check within the TG file, whether the specified custom header is present within your TG. If the specified custom header is found, then Webex Campaign will ingest the file and internally convert that header to the default ‘MSISDN’ header while creating the TG. All the internal file processing will take place using this ‘system-native’ MSISDN header. Therefore, if you download the same target group again from Webex Campaign, it will have the ‘MSISDN’ header and not your custom header.

c) Specifically, this feature is applicable to the following TG creation scenarios:
i. Static TGs created from TG-source = ‘File’
ii. Static TGs created from TG-source = ‘SFTP’
iii. Dynamic TGs created from TG-source = ‘SFTP’
iv. Dynamic TGs created from TG-source = ‘SFTP’ and where the user uploads a ‘sample file’

d) Specifically, this feature is manifested on the following UI screens:
i. ‘Create target group’ pop-up on the ‘Target groups’ list screen
ii. Deployment canvas (when you drag-and-drop the ‘File’ or ‘SFTP’ nodes from the left panel to the central canvas
iii. Seed lists, exclusion lists, inclusion lists which are added on the deployment canvas
iv. Files used for ‘file-drop’ initiated event-triggered instant deployments

e) This feature is not applicable to dynamic TGs created from TG-source = ‘Segment Builder’. In this scenario, you can use the existing ‘ALIAS’ feature within the Segment Builder to change the header from your custom header, say CTN, to the standard default header ‘MSISDN’.
f) For personalization and conditional logic within the SMS / MMS message content, you will need to use the $(TG_MSISDN) attribute.
g) On all the applicable screens within Webex Campaign, the default header label ‘MSISDN’ will be displayed (e.g. Preview & Test, Customer Care, Dashboard, Reports etc.)
h) All the pre-configured reports will continue to display the default header label ‘MSISDN’.
i) If your TG file contains both the headers, MSISDN and your specified custom header, then that file will be rejected by Webex Campaign as an invalid file and the TG will not be created.
j) Similarly, if the file used for ‘file-drop’ initiated event-triggered instant deployments, has records which contain both the headers, MSISDN and your specified custom header, then such records will be rejected by Webex Campaign.

k) This feature is not applicable to API-initiated event-triggered instant deployments; i.e. if you want to use the mobile number of a message recipient as one of the event parameters, then you will need to define that parameter as ‘MSISDN’ and not as your specified custom header name.