AI Dashboards: Datalake Settings
The Datalake Settings page allows you to connect Tango.ad with your Samba Datalake account. Once connected, Tango.ad can access customer, product, and order data to power AI insights, customer segmentation, revenue attribution, and personalized campaigns.
From this page, you can configure authentication, entity IDs, storage options, product mapping, and optional JavaScript transformations for imported data.
For an overview of the AI configuration modules available in Tango.ad, see AI Dashboards Overview.
Best for: Administrators and developers responsible for integrating Tango.ad with Samba Datalake.
Before You Begin
Before configuring the connection, make sure you have:
- A Samba Datalake account
- Your Datalake email and password
- Orders and Products Entity IDs
- Permission to access your Datalake workspace
Datalake Configuration Options
Separate Settings Per Domain
Enable this option if each website/domain should use its own Datalake configuration.
When disabled:
- All domains share one Datalake connection.
- Configuration changes apply across every connected domain.
When enabled:
- Each domain maintains its own credentials and entity configuration.
- Existing settings are copied as a starting point.
For more information about managing websites and domains, see Create and Manage Workspaces and Manage Domains.
Enable Datalake
This switch enables or disables synchronization between Tango.ad and Samba Datalake.
When enabled:
- Customer, order, and product information becomes available to Tango.ad.
- AI features can use imported data.
When disabled:
- No new data is synchronized.
- Existing configuration remains saved.
Datalake data can support AI-powered insights and personalization. See AI Dashboards Overview for more information.
Datalake Email
Enter the email address used to authenticate with your Samba Datalake account.
This account is used whenever Tango.ad retrieves data.
Datalake Password
Enter the password associated with the Datalake account.
The password is securely stored and used only for authentication.
Orders Entity ID
Specify the UUID of your Orders entity inside Samba Datalake.
Tango.ad uses this entity to:
- Import order history
- Calculate revenue
- Analyze purchases
- Build customer insights
Order and revenue data can also support campaign performance analysis through Analytics Overview.
Orders Use Multi-feed Storage
Enable this option if your orders feed has been migrated to Datalake's fixed-column multi-feed storage.
When enabled:
- Tango.ad retrieves orders using multi-feed endpoints.
- Recommended for newer Datalake installations.
Leave disabled if your workspace still uses the legacy entity structure.
Orders Transform Function (Optional)
You can provide custom JavaScript to transform order data before Tango.ad processes it.
Typical uses include:
- Renaming fields
- Removing unwanted attributes
- Normalizing values
- Formatting dates
- Calculating custom fields
This field is optional.
Products Entity ID
Enter the UUID of your Products entity.
This allows Tango.ad to retrieve:
- Product catalog
- Categories
- Brands
- Pricing information
Product information can be used by AI-powered personalization and recommendation features. See AI Dashboards: Scoring Models for information about configuring product and category scoring.
Products Use Multi-feed Storage
Enable this option if your products feed has been migrated to the newer multi-feed storage format.
When enabled:
- Product data is loaded from multi-feed endpoints.
- Better performance for larger catalogs.
Brand Field
Specify the field name that contains each product's brand.
Example:
brand
This field is used by:
- Brand targeting
- Brand boosters
- AI recommendations
- Product segmentation
For more information about brand scoring, see AI Dashboards: Scoring Models.
Category Field
Specify the field that stores product categories.
Example:
categorytext
This field allows Tango.ad to:
- Understand category hierarchy
- Build category audiences
- Apply category scoring
- Power recommendation models
See AI Dashboards: Scoring Models for more information about category-based scoring.
Products Transform Function (Optional)
This optional JavaScript function allows you to modify product records before Tango.ad imports them.
Common examples include:
- Combining fields
- Creating custom metadata
- Formatting product values
- Removing unnecessary attributes
Leave empty if no transformation is needed.
For information about using custom data in Tango.ad, see Meta Fields Overview.
Customers Use Multi-feed Storage
Enable this option if your customer feed has been migrated to Datalake's multi-feed storage.
When enabled:
- Customer lookup uses multi-feed endpoints.
- Subscription status and order matching use the updated storage model.
Leave disabled if using the legacy customer entity.
Customer data can also contribute to AI-powered customer insights and personalization. See AI Dashboards: Traits Mapping.
Saving Your Configuration
After updating any settings:
- Review all configuration values.
- Click Save Changes.
- Tango.ad will use the updated configuration for future synchronizations.
Best Practices
- Verify all Entity IDs before saving.
- Enable Multi-feed Storage only if your Datalake workspace supports it.
- Keep Datalake credentials secure.
- Test data synchronization after making configuration changes.
- Use transform functions only when custom data processing is required.
- Keep Brand and Category field names consistent with your product feed to ensure AI features work correctly.
- Review AI Dashboards: Advanced AI Settings and AI Dashboards: Scoring Models when configuring how imported data influences AI scoring.