Integration Settings

note some of these settings are only available for certain integrations see your integration panel for what's available data ops use aiq's last backup turn this on to freeze your data from this source from the last audience run and discontinue hitting the sources api for new data do not turn this on unless you are switching poss and want to keep the data sync personas / sync contacts enabling this setting allows aiq to keep your customer records aligned between your pos and aiq how it works from pos to aiq updates made to customer profiles in your pos (e g , name, email, phone number, or date of birth) will flow into aiq this ensures that aiq always reflects the most up to date information from your pos from aiq to pos if a customer signs up through an aiq form and no existing match is found in the pos, a new customer profile will be created in the pos automatically important notes the pos remains the source of truth for contact information to change an existing customer’s details, always update the record in your pos syncing begins after this feature is enabled existing records will not be retroactively synced loyalty points, purchase history, and other program data may sync differently depending on your pos integration and loyalty setup sync to relevant market / sync to state enabling this will make aiq only sync contacts that belong to the given credential's region/state mirror archives mirror archives is a dutchie pos–specific feature that ensures order counts remain consistent between your pos and aiq, even when profiles have been archived or merged on the pos side when to use it enable this setting only if your pos has many archived profiles with historic sales attached it is especially useful if your team frequently archives or merges customer profiles in dutchie pos, since it helps maintain a 1 1 relationship between orders in both systems how it works when profiles are archived or merged in dutchie pos, aiq creates a “mirrored” version of those archives to preserve the linked orders this process ensures that your order counts stay accurate and in sync with the pos mirror archives is retroactive , so historic sales attached to archived profiles are also reflected points adjustments if a persona redeemed inflated points before being removed, they may temporarily appear with a negative points balance in most cases, the system will automatically bring the balance back to zero so they can continue earning points going forward custom attributes provide any custom product attributes that you would like to add for reporting and segmenting example 'xyz label' marketing send sms double optins to personas who purchased after send an sms double opt in request if a contact with a phone number had a sale after/on this date takes 24 hours to trigger send sms double opt in if this setting is removed later on it can cause loyalty profiles to be lost if they only used this setting to become a member and did not use a signup form thus, we do not recommend changing this after it is set loyalty enroll personas in loyalty program who purchased after automatically signup contact for the loyalty program if they had a sale after/on this date contact then earns points for sales after/on this date takes 24 hours to reflect loyalty points imported on if a date is filled in we will pull in loyalty points and stop afterwards from posabit, use this in conjunction by turning on the loyalty points within aiq by heading to settings > loyalty > points accrual start date and set that for the following day all users are age compliant with my industry? required! required! all users from this source have passed an age gate compliant with my industry mirror integrations loyalty point values? pull points from the pos, but keep the loyalty settings within that pos faqs can we use the " enroll personas in loyalty program who purchased after" option for only some of the api keys, not all? i'm adding a new location, but i don't want the new customers to be able to accrue points until a certain date no, this setting would apply for all locations instead, we recommend using the point zero feature on an audience and zeroing sales from the specific location (you can set a date range) they'll be marked as "loyal", but sales from the new location wouldn't get points how to troubleshoot synchronization and product mapping issues between aiq ecommerce and external systems (e g , flowhub) integration between aiq and external platforms—such as flowhub—ensures that product data, images, and categories remain consistent across your systems however, synchronization or product mapping issues may occasionally prevent products from appearing correctly or delay updates this guide outlines common causes, troubleshooting steps, and best practices to maintain a smooth integration troubleshooting product mapping and visibility products not appearing in the aiq ecommerce menu if certain products are visible through search or offers but missing from the aiq ecommerce menu, the issue may be tied to incomplete category or subcategory mapping to resolve this in aiq, navigate to menu > categories > \[your category] > pos mapping under pos mapping , enter the exact subcategory name listed under the product’s advanced tab (e g , “pre rolled cannabis joints”) select create , then click save to finalize the mapping return to the products page and scroll to the bottom to click sync once synchronization completes, verify that the product appears in its assigned category in the aiq ecommerce menu addressing synchronization delays product image updates not appearing immediately if product images or details updated in flowhub don’t appear right away in aiq, the delay is often due to the automated sync interval or api update timing from your pos provider to manually trigger an update go to menu > products in aiq click the sync button to start a manual synchronization allow the sync process to complete—this may take several minutes recheck the product listing to confirm that the updated image or data has populated if the issue continues after manual sync, the delay likely stems from your pos system’s refresh timing check back after the next scheduled sync or contact your provider for further review best practices for consistent synchronization confirm accurate mapping regularly verify that categories and subcategories are properly mapped to prevent missing or misclassified products run manual syncs when needed trigger manual synchronizations for time sensitive updates instead of waiting for automated cycles review data integrity ensure product details (name, sku, and subcategory) match exactly between systems to avoid mapping errors monitor integration health if repeated sync failures occur, reach out to your pos provider or aiq support to confirm integration status and api health