Overview

Agentforce Commerce integration connects to the OCAPI Data API to collect orders and code versions, and to the Admin API to monitor sandbox usage. There are three configuration areas: OCAPI credentials, Sandbox API credentials, and sandbox contract allowances.

1. OCAPI API Client Setup

The OCAPI client is used to collect orders and code version data from your Commerce Cloud instance.

1. Log in to Account Manager at account.demandware.com.
2. Navigate to API Client and create a new API client (or use an existing one).
3. Under Token Endpoint Auth Method, select client_secret_post.
4. Under Scopes, add the sfcc.orders and sfcc.code-versions scopes (or use a wildcard scope if your organization allows it).
5. Note the Client ID and generate a Client Secret.
6. Ensure the client is added to the appropriate OCAPI Data API configuration on your instance under Administration > Site Development > Open Commerce API Settings.

2. Sandbox API Client Setup

A separate API client is used to query sandbox credit usage via the Commerce Cloud Admin API.

1. In Account Manager, create (or reuse) an API client.
2. Assign the Sandbox API User role to the client. Without this role, sandbox API calls will return 401 errors.
3. Note the Client ID and Client Secret.
4. Find your Realm identifier (e.g., abcd) — this is the four-character code for your organization.

3. Sandbox Contract Allowance

Optional fields that enable contract-level credit tracking on the Sandboxes dashboard page.

• Usage Start Date — The start date for tracking credit usage (YYYY-MM-DD).
• Contract Credits — The total number of credits in your contract (e.g., 600000).
• Contract Expiration — When your contract expires (YYYY-MM-DD).

4. Configure in Rogue Alerts

1. Go to Settings > Sites and enable the Salesforce Commerce Cloud toggle.
2. The SFCC configuration fields will appear below the site list.
3. Enter the fields below and click Save.

Field	Description
Instance Hostname	Your Agentforce Commerce instance hostname, e.g. your-instance.dx.commercecloud.salesforce.com
Client ID	Account Manager OCAPI client ID
Client Secret	Account Manager OCAPI client secret
Realm	Your four-character realm code
Sandbox Client ID	Sandbox API client ID (with Sandbox API User role)
Sandbox Client Secret	Sandbox API client secret
Usage Start Date	Optional — start date for credit tracking
Contract Credits	Optional — total credits in your contract
Contract Expiration	Optional — contract expiration date

Shopify integration connects to the Admin API to collect order data for your Shopify stores. Configuration is per-site — each Shopify store is added as a site in Rogue Alerts with its own credentials.

1. Create a Custom App in Shopify

1. Log in to your Shopify admin at your-store.myshopify.com/admin.
2. Go to Settings > Apps and sales channels > Develop apps.
3. If prompted, click Allow custom app development.
4. Click Create an app and give it a name (e.g., "Rogue Alerts").
5. Under Configuration > Admin API integration, click Configure.
6. Select the read_orders access scope. Add read_products if you want product-level detail in the future.
7. Click Save, then click Install app.
8. After installation, go to API credentials and copy the Admin API access token. This token starts with shpat_.

2. Add the Site in Rogue Alerts

1. Go to Settings > Sites in the dashboard.
2. Enable the Shopify toggle and click + Add Shopify Site.
3. Enter a Site ID (a short identifier, e.g., my-store) and a Display Name.
4. Set Platform to Shopify. The Shopify config fields will appear.
5. Enter the fields below and click Save.

Field	Description
Shop Domain	Your Shopify store domain, e.g. my-store.myshopify.com
Access Token	The Admin API access token from your custom app (shpat_xxxx)

The Teams integration sends alert notifications to Microsoft Teams channels using Incoming Webhooks (via Teams Workflows). No Azure AD app registration, admin consent, or Graph API permissions are required — just a webhook URL for each channel you want to post to.

1. Create a Webhook for Each Channel

Repeat these steps for each Teams channel you want to receive alerts in:

1. In Microsoft Teams, right-click the target channel and select Workflows.
2. Search for and select "Post to a channel when a webhook request is received".
3. Give the workflow a name (e.g., "Rogue Alerts") and click Next.
4. Confirm the channel and click Add workflow.
5. Copy the generated webhook URL. It will look like https://prod-xx.westus.logic.azure.com:443/workflows/...

2. Configure in Rogue Alerts

1. Go to Settings > Communication and enable the Microsoft Teams toggle.
2. The Teams configuration fields will appear.
3. In the Channel Webhooks textarea, enter one webhook per line in name=url format.
4. Click Save.

Field	Description
Channel Webhooks	One entry per line: name=webhook-url. The name is a short label you choose (e.g., alerts, ops, incidents) — it's used in alert routing to specify which channel(s) receive each alert type.

Example:

---

3. Configure Alert Routing

After saving your webhooks, configure which alerts go to which channels.

1. Go to Settings > Alerts.
2. For each alert type you want routed to Teams, set Notify Via to Teams.
3. In the Destination field, enter the webhook name(s) — e.g., alerts or alerts, ops (comma-separated for multiple channels).
4. If you leave the Destination blank, the notification will be sent to all configured webhooks.
5. Click Save Alert Settings.

The Slack integration sends alert notifications to Slack channels using a bot token. When incidents are opened or resolved, messages are posted to the channels you configure per alert type.

1. Create a Slack App

1. Go to api.slack.com/apps and click Create New App.
2. Choose From scratch.
3. Name the app (e.g., "Rogue Alerts") and select your workspace.
4. Click Create App.

2. Add Bot Permissions

1. In the app settings, go to OAuth & Permissions in the left sidebar.
2. Scroll to Scopes > Bot Token Scopes.
3. Click Add an OAuth Scope and add chat:write.

3. Install the App and Copy the Token

1. Scroll to the top of the OAuth & Permissions page and click Install to Workspace.
2. Review the permissions and click Allow.
3. Copy the Bot User OAuth Token. It starts with xoxb-.

4. Invite the Bot to Your Channel(s)

The bot can only post to channels it has been added to.

1. Open the Slack channel where you want alerts posted.
2. Type /invite @YourBotName (replace with the name you gave your app).
3. Repeat for each channel you want to use.

5. Configure in Rogue Alerts

1. Go to Settings > Communication and enable the Slack toggle.
2. The Slack configuration fields will appear.
3. Paste your Bot Token and click Save.

Field	Description
Bot Token	Bot User OAuth Token from your Slack app (xoxb-...)

---

6. Configure Alert Routing

After the bot token is saved, configure which alerts are sent to Slack and to which channels.

1. Go to Settings > Alerts.
2. For each alert type you want routed to Slack, set Notify Via to Slack.
3. In the Destination field, enter the channel name(s) — e.g., #alerts or #alerts, #ops (comma-separated for multiple channels).
4. Click Save Alert Settings.

---

7. Send Alerts Directly to a Person

Slack bots can send direct messages to individual users. Instead of a channel name, use the person's Slack member ID in the Destination field.

How to find a member ID:

1. In Slack, click on the person's name or profile picture to open their profile.
2. Click the three-dot menu (…) in their profile panel.
3. Select Copy member ID. It will look like U01ABC123XY.

Paste the member ID into the Destination field for the alert type you want to route to that person. You can mix channels and member IDs — for example: #incidents, U01ABC123XY sends to both the channel and the person.

CrUX provides real-user performance data from Chrome browsers, showing how actual visitors experience your site. Rogue Alerts collects CrUX data for your configured domains and displays Core Web Vitals metrics on the Performance page.

What CrUX Measures

• LCP (Largest Contentful Paint) — How quickly the main content loads.
• INP (Interaction to Next Paint) — How responsive the page is to user interactions.
• CLS (Cumulative Layout Shift) — How much the page layout shifts while loading.
• TTFB (Time to First Byte) — How fast the server responds.

Data is broken down by device type (desktop, phone, tablet), navigation method, and page type.

1. Enable CrUX

1. Go to Settings > Performance and enable the CrUX (Chrome UX Report) toggle.

2. Configure Per-Site Domains

CrUX data is collected per-site based on the domain configured for each site.

1. Expand a site on the Settings > Performance page.
2. Set the Domain field to your site's public domain (e.g., www.example.com).
3. Click Save.

CrUX data will appear on the Performance page once the collector runs. Data is updated weekly by Google, so new domains may take a few days to show results.

3. Page Types (Optional)

You can configure CrUX to collect data for specific page types (homepage, PLP, PDP, category) in addition to the overall origin. Expand the CrUX section in the site card and add URL patterns for each page type.

Uptime monitoring pings your URLs at regular intervals with a HEAD request and reports whether each URL is reachable. When a URL goes down, an incident is opened and notifications are sent based on your alert configuration.

How It Works

• Each URL is checked with an HTTP HEAD request.
• A successful response (any 2xx or 3xx status) marks the URL as Up.
• Blocked responses (401, 403, 429, 451) are reported as Blocked.
• All other failures are reported as Down.
• Response time is tracked and averaged over time.

1. Enable Uptime Monitoring

1. Uptime monitoring is always enabled for configured site domains.

2. Configure URLs

1. Go to Settings > Uptime Monitoring to add additional URLs.
2. In the Monitored URLs textarea, enter one URL per line.
3. Click Save.

Field	Description
Monitored URLs	One URL per line. Each URL will be checked with a HEAD request. Example: https://www.example.com https://api.example.com/health