# Channels, Store appearance, Integration and Connection log

> The channels, store appearance, integration and connection log screens in the Setup group; choosing the design of the review section and monitoring how your site and store system connect to Sayproof.

Source: /en/features/setup-screens/

The **Setup** group in the menu contains six screens; this page covers the four that relate to your site's connection to Sayproof. **Users** and **Settings** have their own pages: [Users and roles](/en/features/users.md), [Settings](/en/features/settings.md). The setup steps are described in detail in the developer documentation; this page summarises the content of each screen.

## Channels

The screen has four tabs. The single sentence above each tab explains what the tab is for.

| Tab | Content |
|---|---|
| **Channels** | The points of sale where you collect and show reviews. Each channel card contains a setup checklist: domain verified, site key ready, invitation landing page set. The last step is optional; if no page is set, "optional" is shown next to it. If the domain or the site key is missing, the **Finish setup** button resumes the setup from where it was left. The card's **Edit** button changes the channel's name, language, invitation landing page and whether it is on; the same form takes the channel's **Name shown to customers**, **Sender email address** and **Support page address** used in emails ([Editing a channel](/en/integrate/channels-and-keys.md#editing-a-channel)). When the number of open channels reaches the **Channel allowance**, the **Set up a channel** button is replaced by **Request another channel** ([Channel allowance](/en/integrate/channels-and-keys.md#channel-allowance)). |
| **Domains** | The **Domains** card lists the domains on which reviews can be shown, with their status; reviews only appear on pages of verified domains. A new domain is added here; for every domain waiting for verification, a "How to verify `<domain>`" section below the card shows the **Verification method** choice (**File on your site** or **DNS record**), the chosen method's values with copy buttons, and the **Verify** button ([Domain verification](/en/integrate/channels-and-keys.md#domain-verification)). A domain is deleted with **Remove** ([Removing a domain](/en/integrate/channels-and-keys.md#removing-a-domain)). The **Sender domains** card verifies your domain so that invitation emails can leave from your brand's address; a verified domain's **Go to Invitation sending › Sending route** button opens the **Invitation sending** screen ([Channel, domain and keys › Sender domains](/en/integrate/channels-and-keys.md#sender-domains)). |
| **Keys** | The **Site keys** and **Server keys** cards, and the collapsed **Advanced: signing passwords** section at the bottom. As the sentence above the tab says, two keys are enough: the site key sits in your page and isn't secret; the server key is secret, and your store's server uses it to prepare pages and send orders. Server keys are created on this tab; the **Server keys** table has no permission column, and every server key created in the panel can send orders and prepare pages. A site key is created in the channel's setup wizard or with the **New site key** button on this tab; to replace a key, create the new one first, update the code on your site, then cancel the old one ([Replacing a key](/en/integrate/channels-and-keys.md#replacing-a-key)). Optional signing passwords are created on the **Signing passwords** card in the advanced section; the table's **Password ID** column is the value sent in the `X-Sayproof-Secret` header of signed order requests. Keys and passwords are also cancelled on this tab. |
| **Page check** | Checks whether a product page that shows reviews in your own design contains the required elements in the page as it first loads ([Required elements › Page check](/en/customize/required-elements.md#page-check)). |

This screen is only open to the **Administrator** role. For details, see [Channel, domain and keys](/en/integrate/channels-and-keys.md).

## Store appearance

This screen chooses, per channel, how the default component looks, that is the review section on the product pages where you do not draw it with your own design.

| Section | Content |
|---|---|
| **Channel** | The channel whose look is changed; the list shows the channel's name and market. If a channel is selected in the top bar, the screen opens with that channel; choosing here also changes the channel in the top bar. With unsaved changes, switching the channel or leaving the screen asks for confirmation first. |
| **On your site now** | How reviews were shown on this channel's product pages in the last 7 days: on how many product pages the default component is used, on how many the look is chosen in your site's code (with the chosen layout and design), on how many reviews are shown with your site's own design, and what width the review area mostly has. If the channel was not seen on your site in the last 7 days, this is said too. |
| **Design** | One of eight built-in designs; each option's card shows a short description of the design (see the table below). New channels use **Warm**. |
| **Layout** | **Cards** (summary and rating bars on top, each review in its own card) or **Side panel** (on wide screens the summary on the left and the reviews on the right; on narrow screens stacked). New channels use **Cards**. |
| **Preview** | The review section built with your choices. It is built from the reviews of the product with the most published reviews in the channel's market, in the channel's language; the product's name is shown above the preview. The **Phone** (375 px), **Tablet** (768 px) and **Wide screen** (1200 px) buttons, and **Width on your site** when your site has reported one, choose the width of the preview; a preview that does not fit your screen is shown scaled down. The sentence above the preview says how the component is arranged at that width. |

The design options and the descriptions shown in the panel:

| Design | Description |
|---|---|
| **Warm** | Cream summary panel, yellow stars, coloured initials; warm and soft. |
| **Trust** | Green score box and accents; puts the verified buyer first. |
| **Editorial** | Black and white, large score, quoted titles; photos come first. |
| **Minimal** | White and light grey with a thinly framed summary; a calm look that fits any store. |
| **Blush** | Blush pink tones, pink stars and round corners; for beauty and fashion. |
| **Sport** | Black score box, orange stars, upper-case titles and sharp corners; for sports and outdoor. |
| **Natural** | Earth and olive tones; for home, living and natural products. |
| **Night** | Dark background with light text; for dark websites. The review section brings its own dark background. |

For the colour and corner values of the designs and how your developer can change them, see [CSS variables › Built-in designs](/en/customize/theme.md#built-in-designs).

On a wide screen the preview sits to the right of the choices and stays in view while you scroll.

The choice on this screen only applies to pages that use the default component. What applies on your site is decided in this order:

1. If reviews are shown with your site's own design (headless use, or your site's code reading reviews without the script), the choice on this screen does not appear on the site. If every page on the channel works this way, the design and layout choices are turned off and a warning says so.
2. If the look is chosen in the page's code (`data-review-style`, `data-review-theme`, an option given to the script, or `style` and `theme` in the server-rendering request), the code applies on that page.
3. On the other pages, the choice saved on this screen applies.

Style rules written by your developer take precedence over the chosen design; Sayproof cannot see them. The component changes its arrangement with the width of the review area, not the page: when the area is narrower than 880 px, the **Side panel** layout does not open a side panel and the summary stays above the reviews.

When a choice changes, the preview is refreshed at once; the choice itself does not apply on your site until it is saved. While there is an unsaved choice, the **You have unsaved appearance changes** bar appears at the bottom of the screen: **Save changes** saves the choice and **Cancel** returns to the channel's saved look. If you choose another channel without saving, you are asked whether to discard the changes; **Discard changes and switch** switches, **Cancel** keeps you on the same channel. The saved change is recorded in the **Activity history** and shows on your site once the cache time of Sayproof's answers (at most 60 seconds) has passed.

When the preview cannot be shown, the reason is given: if the channel has no site key in use, a site key must first be created on the **Channels** screen; if there are no published reviews in the channel's market, no preview is built. The preview uses only Sayproof's styles; the changes you make on your site with CSS variables or CSS rules do not show in the preview.

The choice affects only the default component; in headless use, your own design determines the review section. If the `data-review-theme` or `data-review-style` attribute is used in your page's code, the channel's choice does not apply to that container ([Layout and CSS selectors](/en/customize/css-hooks.md#layout)). In every design, colours, typeface and corners can be matched to your theme with [CSS variables](/en/customize/theme.md).

This screen is only open to the **Administrator** role.

## Integration

Connecting Sayproof to your site takes two jobs, and both are needed: showing reviews on your product pages and sending orders to Sayproof. Without orders nobody can write a review and no invitations are sent.

The screen has six tabs. The single sentence above each tab explains what the tab is for. If you have more than one channel, you first choose the **Channel** on the **Showing reviews** and **Order transfer** tabs (if a channel is selected in the top bar, the screen opens with that channel, and choosing here also changes the channel in the top bar); the values, the **Seen on your site?** section and the **Latest orders received** line are prepared for the chosen channel. The panel shows the values to use in the setup; your developer does the setup, and the code samples are in this documentation and in the setup guide sent from the **Share with a developer** tab.

| Tab | Content |
|---|---|
| **Showing reviews** | The **Show reviews on the product page** card. The **Setup route** choice offers three routes: **Script (in the browser)**, **Next.js (on the server)** and **Django / Jinja (on the server)**; a one-sentence description appears under the chosen route (the script works on any site and reviews load after the page opens; with Next.js and Django, reviews arrive with the page and search engines also see the review text and rating; see [SSR](/en/integrate/server-rendering.md)). The **Values for the setup** list shows the **Site key** and the **Sayproof address** with copy buttons, plus the **Script address** on the script route, or the **Channel code** and a **Server key** row on the server routes; because the server key is secret and shown only when created, that row has no value but a **Go to keys** button. Below it, the **Step-by-step setup (docs)** button opens the documentation page of the chosen route ([Script](/en/integrate/script.md), [Next.js](/en/integrate/nextjs.md), [Django](/en/integrate/django.md)), and the **Share with your developer** button switches to the **Share with a developer** tab. The same values are shown in the **How to connect** step of the channel setup wizard ("The values to give your developer"); that step also carries the **Go to order transfer** and **Share with a developer** buttons for order transfer. The Below it is the **Seen on your site?** report for the chosen channel ([below](#seen-on-your-site)). |
| **Order transfer** | The two ways are shown one under the other; each says under its own heading when it is used. **Read from your platform**: the **Platform connections** card; if there is a ready connection for your store platform (Akinon, Shopify, WooCommerce), Sayproof reads the orders itself. Each connection's card shows the last read, the orders that could not be read and the **How statuses are matched** table; a saved connection's address, read frequency and (for an Akinon connection) channel number on the platform are changed with **Edit the connection**. See [Akinon orders](/en/integrate/akinon.md), [Shopify orders](/en/integrate/shopify.md), [WooCommerce orders](/en/integrate/woocommerce.md). **Sent by your store**: the **Send orders and deliveries** card and the **Status values to send** table. The card holds the **Values for the setup** list (the **Orders** and **Deliveries** addresses and the **Channel code**, with copy buttons; a **Server key** row with a note that the order-sending system uses this key on every request, and a **Go to Channels › Keys** button), a short note, the **Step-by-step setup (docs)** and **Share with your developer** buttons, the **Latest orders received** line, the status counters and the **Test the connection** action ([Sending orders and deliveries](/en/integrate/orders.md)). The **Latest orders received** line shows how many orders arrived for the chosen channel in the last 7 days and in total, and when the last one arrived; the request figures and the **Recent requests** list in the **Order transfer status (all channels)** section cover all channels. |
| **Email delivery events** | Only shown if your own system sends the invitations. The **Email delivery events** card: whether it is connected, the latest notice, the number of notices received in the last 7 days by type, and the addresses to enter in your email service. For emails Sayproof sends, this comes in automatically. For details, see [Email delivery events](/en/integrate/email-events.md). |
| **Google product reviews** | Only the **Administrator** role sees it. One card for each open channel: **Create address** produces the **File address** to add in Google Merchant Center (with a copy button); **Renew address** closes the old address and produces a new one, **Close address** closes it, and both ask for confirmation. The card shows how many times Google has fetched the file and when it last did, the **Reviews in the file (<market> market)** number against the 50 review threshold, the **Reviewed products in the file** and **Products without a GTIN or an MPN with a brand** numbers, the number of reviews that can't go into the file with the reason, and the **Steps to add it in Merchant Center (documentation)** button plus, when needed, **Go to product sources**. The numbers cover all reviews of the channel's market. For details, see [Google product reviews](/en/integrate/google-reviews.md). |
| **Share with a developer** | Links to a **setup guide** sent to the developer who sets things up, without opening a panel account for them. In the **Share a guide** wizard you choose the channel, the guide language (Turkish or English), the setup path (script, Next.js, Django / Jinja or all three), whether order transfer is explained too, how many days the link stays open (7, 30 or 90) and an optional note. The guide contains the channel's addresses, site key, channel code, verified domains, code samples and documentation links; the order example uses `Authorization: Bearer <server-key>`. The server key is not in the guide; if needed, create it under **Channels › Keys** and send it to the developer separately. The developer opens the link and can print the guide, save it as PDF or download it as Markdown. The site key in the guide is the channel's newest key. The **Shared setup guides** list shows each link's status, end date and how many times it was opened; it lists every link whose status is **Open** and the newest 50 of the links that have expired or been closed. The **Copy link** and **Close link** buttons are here. A link that has expired or been closed no longer opens. |
| **Marketplace reviews** | Only the **Administrator** role sees it. Used to show, with their source, the buyer reviews written for your store on marketplaces such as Trendyol or Hepsiburada on your product pages: you set up a marketplace connection, the reviews are read from a file or a link address, and each connection's card shows the report of its last read. For details, see [Marketplace reviews](/en/features/marketplace-reviews.md). |

Only the **Administrator** role can see and share the setup values and addresses; other roles see the status cards and the **Status values to send** table on the **Showing reviews** and **Order transfer** tabs, and do not see the **Google product reviews**, **Share with a developer** and **Marketplace reviews** tabs. The **Share with a developer** tab is the easiest way to pass the values and addresses to your developer; you can also refer them to the [Setting up](/en/integrate/overview.md) section of this documentation.

### Seen on your site?

A report that tells whether the setup actually works by looking at the requests that come from your site. The badge next to the heading gives the overall result: **Setup is working**, **Some things need attention**, **Not seen in the last 7 days** (seen before but not loaded in the last 7 days), **Not seen yet** or **Requests are being turned away** (the review section has never loaded and requests were turned away). Each row in the list below the badge is one check; the mark at the start of the row gives the result and the text gives the details:

| Check | What it looks at |
|---|---|
| Loading | How many times the review section loaded on how many product pages in the last 7 days, and when it last loaded. If it hasn't loaded for 7 days, the row says the code may have been removed or the page changed. |
| Turned-away requests | The number of requests turned away in the last 7 days and the reasons; each reason row shows the site the request came from, the reason and the number of requests. If the reason is an unverified domain, a **Go to domains** button appears, otherwise **See turned-away requests**. |
| Product codes | Whether the product codes the site sent in the last 7 days are in your catalogue or reviews. Up to five unrecognised codes are shown as examples; this usually means the site sends another code, such as the model code instead of the variant code. The **Go to products** button opens the **Products** screen. |
| Server rendering | Only shown if pages are prepared on the server: the number of requests from the server and whether the script also loads in the browser. If the script doesn't load, the review form can't open. |
| Review form | How many times the review form was opened in the last 30 days and how many reviews were sent. If it was never opened, the row suggests opening the form on the page yourself to test it. |
| Coverage | How many of the products with live reviews had the review section seen on their page in the last 30 days. This row is for information; if a channel is chosen, the reviews in that channel's market are counted. |
| Errors | Only shown if requests ended with an error on Sayproof's side in the last 7 days; if it continues, you're asked to report it with the record number from the **Connection log**. |

Two tables follow the checks:

- **Product pages where the review section loaded in the last 7 days:** up to 10 products, with the **Product**, **Status** (**Reviews shown**, **No reviews yet** or **Product code not recognised**), **Loads (7 days)** and **Last load** columns.
- **Sites the requests came from (last 30 days):** the **Site** (**Store server** for requests from the server), **Domain** (verified or **Not verified**), **Requests (30 days)**, **Turned away** and **Last request** columns. Verified domains with no requests in the last 30 days are listed too, with 0 requests.

At the bottom are the number of product page views in the last 7 days and the **Go to the connection log** button. Roles other than Administrator see the same report for all channels, without the buttons that lead elsewhere.

When the setup breaks, the **Needs your attention** card on the **Overview** screen warns you too: if requests from your site were turned away in the last 7 days, or if the review section, which loaded at least 20 times in the previous 7 days, hasn't loaded for 48 hours ([Reports](/en/features/reports.md)).

## Connection log

A record of every request your site and store system make to Sayproof: review lists, review submissions, order and delivery transfers, email delivery events. If you are told that "reviews aren't showing" or "orders aren't arriving", check this screen first: it shows whether the request arrived, whether it was turned away and what the result was.

- **Table:** the **Result**, **Request type**, **Site**, **Market**, **Product**, **Response**, **Time**, **Record no.** and **Date** columns. Successful requests show the result **Succeeded**. The **Response** column shows, depending on the request type, the number of reviews returned or orders or records accepted ("3 reviews", "1 order", "2 records"); other requests and refused or failed requests show "—". For requests made with a server key or a password that carry no site address (for example SSR and order transfer), the **Site** column reads **Store server**. Older rows recorded without a type show "Unknown (older record)" as the **Request type**. The **Date** column shows the date and time together.

- **Counters:** **Requests**, **Typical response time**, **No reviews found**, **Refused** and **Errors**. The counters follow the filters other than the result (market, **Request type**, language, domain), the search, the dates and the channel selected in the top bar. With no dates chosen, the first counter names the kept period ("Requests (last 30 days)"); with dates chosen, it reads "Requests (chosen dates)". Clicking **No reviews found**, **Refused** or **Errors** filters the list to that result (**Refused** shows every refused request), and **Requests** clears that filter; the counters themselves do not change.
- **Filters:** result, **Request type** (**Review list**, **Review list from your server**, **Customer's own reviews**, **Reviews on the order page**, **Review sent**, **Order transfer**, **Delivery transfer**, **Email delivery event**, etc.), market, language, domain and **Only refused requests**. To filter by channel, use the **Channel** selector in the top bar; when a channel is selected, the list shows only that channel's requests. The search looks in the product code, the record number and the site address.
- **Sorting:** **Newest first**, **Oldest first** or **Slowest first**.
- Clicking a row shows the request type, the response, the time taken, a text explaining the result of the request and the record number. Depending on the kind of key the request was made with, it shows **Site key used**, **Server key used** or **Signing password used** (with the password's name); for email delivery events, the **Email service** that sent the notice is shown instead.

Entries are kept for 30 days. For the meaning of the results, see [Troubleshooting](/en/integrate/troubleshooting.md).