aligns your data with the Australian Tourism Data Warehouse (ATDW). This ensures your experience information is accurate and consistent across all ATDW platforms, reducing errors. For example, map your internal "Tour Name" field to the ATDW "Product Name" field for seamless synchronisation.
Accessing this feature
Go to Settings > ATDW Integration Settings > Data Field Mapping
How to use it
The ATDW Data Field Mapping tool provides a structured approach to linking your internal data fields with ATDW requirements. Follow these steps to configure and manage your data mappings:
Select ATDW Experience Type: Upon entering the mapping interface, first select the specific ATDW experience type you intend to map (e.g., Listing, Event, Offer). This selection will dynamically load the relevant ATDW fields for that experience category.
Identify Local Data Source: On the left side of the interface, your organisation's available internal data fields will be displayed. These fields are typically drawn from your connected CRM, booking system, or content management system. Review this list to understand your source data.
Map Fields: For each ATDW field listed on the right, identify the most appropriate corresponding local data field from the left panel. Drag and drop the local field onto its ATDW counterpart, or use the dropdown selector next to each ATDW field to choose a source field. The system may offer automated suggestions for common field names (e.g., "Experience Name" to "ATDW Experience Name"). Review and confirm these suggestions.
Configure Mapping Logic (Optional):
One-to-One: Direct transmission of data from a local field to an ATDW field.
Custom Transformation: For more complex scenarios, you may need to apply transformation rules. This could involve concatenating multiple local fields into one ATDW field (e.g., "Street Number" + "Street Name" into "ATDW Address Line 1"), or applying conditional logic (e.g., if local "Category" is X, map to ATDW "Theme" Y).
Default Values: If a local field has no direct ATDW equivalent or is frequently empty, you can set a default value to be used for the ATDW field during synchronisation. This ensures that essential ATDW fields are never left blank.
Handle Unmapped ATDW Fields: Any ATDW fields that remain unmapped will either receive a default value (if configured), or they will be left blank during synchronisation, potentially leading to incomplete ATDW listings. It is recommended to map all essential ATDW fields.
Review and Validate: Before saving, carefully review all configured mappings. The system provides a validation check that highlights potential issues, such as incompatible data types or missing required fields. Address any warnings or errors.
Save Mappings: Once satisfied with the configuration, click the Save Mappings button. This action stores your mapping profile. You can create and save multiple mapping profiles for different experience types or specific integration needs.
Test Synchronisation: After saving, initiate a test synchronisation for a sample experience. This allows you to preview how your mapped data will appear in ATDW without affecting live listings. Review the test results for accuracy and completeness.
Tips
To maximise the efficiency and accuracy of your ATDW data synchronisation, consider these tips:
Understand ATDW Requirements: Thoroughly familiarize yourself with the ATDW data specifications for each experience type. This knowledge is crucial for making informed mapping decisions and ensuring compliance.
Prioritise Mandatory Fields: Begin by mapping all mandatory ATDW fields. This ensures your listings meet basic ATDW requirements and are eligible for publication.
Maintain Source Data Quality: The accuracy of your ATDW data directly depends on the quality of your internal source data. Regularly audit and cleanse your local databases to ensure data consistency and minimise errors during synchronisation.
Document Custom Mappings: For any complex transformations or default values, maintain clear internal documentation. This helps in understanding the logic, troubleshooting issues, and onboarding new team members.
Test Extensively: Use the test synchronisation feature for new mappings or significant changes. Test with a variety of data sets, including edge cases, to identify and resolve any mapping discrepancies before live deployment.
Regularly Review Mappings: ATDW specifications can evolve, and your internal data structures may change. Periodically review your mapping profiles (e.g., quarterly or biannually) to ensure they remain current and effective.
Collaborate with Data Owners: Work closely with the teams responsible for managing your internal data. Their insights into data definitions and usage can be invaluable for accurate and complete mapping.
Need help?
For further assistance, contact us at [email protected]