Lusca

Getting started

Lusca installation guide

Prepare access, create one workspace, connect Shopify, then add Google Ads, Merchant Center, Search Console and Google Analytics when needed.

Create my workspace
01

Before installation

  • Shopify admin access.
  • An email that can access Google Ads.
  • An email that can access Merchant Center if available.
  • Search Console access if the property already exists.
  • Google Analytics access if a GA4 property is available.
  • To read orders, install Lusca and grant the displayed Shopify permission. Protected actions keep their separate controls.
02

If access is missing

  • Continue with Shopify only for the first catalog audit.
  • Invite the agency or Google admin later.
  • Add Merchant Center, Search Console or Google Analytics later without recreating the store.
  • A missing account, scope or gate closes only the affected capability.
03

Example ChatGPT questions

  • Which active products have low stock, and which Ads campaigns are currently delivering?
  • Since installing Lusca, how did sales change over the last 60 days?
  • Which products are in stock in Shopify but disapproved in Merchant Center?
  • If this action is available, prepare a protected card to move this product to draft without applying it.
  • If this action is available, prepare a protected card to pause this Ads campaign without applying it.
04

Capabilities and safeguards

  • Installation with Shopify order-read permission automatically enables 60-day order analysis for this exact store. Uninstalling Lusca or revoking that permission stops access.
  • Shopify and Ads actions remain unavailable without the exact scopes and production PostgreSQL.
  • When available, these actions pass only through a protected card, a human click and one reserved attempt.
  • Merchant Center, Search Console and Google Analytics 4 remain read-only.
  • Merchant or Google results are sent to ChatGPT only after the exact workspace has the required separate versioned activation; ChatGPT account settings remain under that user's control.
  • An ambiguous provider outcome is never retried automatically; only a read-only recheck is allowed.