The following are the access scopes of our Selleasy app, obtained from Shopify.
Access Scopes | Purpose |
read_price_rules & write_price_rules | For dynamic discount creation. |
write_discounts | For discount code creation - all types. |
read_products & write_products | For reading products and writing metafields. |
read_product_listings | For product validation and product status checks. |
read_orders | To check orders for metrics, conversion purposes, and billing. |
write_orders | Tag orders on conversion from the app. |
read_locations | To get the inventory of products across locations. |
read_script_tags | To check app’s script tag in the store. |
write_script_tags | To add script tags to the store. [Deprecated] |
read_inventory | Read product’s inventory for campaign configurations. |
read_themes | To check and notify users about the status of app blocks and app embeds. |
write_metaobjects
read_metaobjects
read_metaobject_definitions
write_metaobject_definitions | To store campaign details and app’s configurations for storefront access. |
read_locales | To enable merchants to configure campaigns for different locales. |
read_draft_orders, write_draft_orders | To enable merchants to run after-sale (post-purchase) campaigns. |
write_order_edits | Edit orders for after sale campaigns. [Not used as of now] |
unauthenticated_read_metaobjects
unauthenticated_read_product_listings
unauthenticated_read_product_tags
unauthenticated_read_product_inventory | Used for campaign configurations and validations in storefront. |
read_customer_events | To capture the checkout status/event for triggering conversion tracking in the app. |
write_pixels | Used for creating app pixel for conversion tracking. |
read_customers | To enable merchants to personalize campaigns for customers. |
Data storage and usage
Customer data
- We fetch customers’ information and show it to merchants when they configure campaigns targeting specific customers in our app.
- At no point is this information stored in the database or anywhere else.
- Only when merchants configure customer conditions in a campaign, the Shopify’s unique customer ID will be saved.
- This information is stored at the campaign level. Changing or deleting a campaign’s configuration will remove this information.
Please feel free to contact our customer support team if further clarifications are required.