Docs for agencies

• Markup hooksThe data-blok and data-cast attributes that reliably identify a block or a part of the store.
• Blocks and fieldsEvery kind of page block and its fields: text, links, images and options.
• Website presetA website saved as a JSON file: theme, pages and the store homepage.

Getting started

1. Create a store or a website on the sign-up page. Your first store can be your own, just for trying things out.
2. As a programme partner, you create a store for a client through a link with your code: when signing up from the partner's contact address, choose “I am creating this store for a client”. This creates a development store: customers cannot see it, nothing can be bought or billed in it, and you browse it through a preview from the Subscription screen. Custom CSS is switched on in it from the start. An inactive store is put to sleep by the platform, and nothing in it is deleted.
3. When the store is ready, you hand it over to the client with an invitation from the Subscription screen. On takeover the client adds the company details, sets up their sign-in and decides which of your people keep access; the client then opens the store to customers.
4. As a partner you have the Partner portal at admin.portican.com: the stores Portican has assigned to you and their status, your codes with a sign-up link, commissions by month and payouts. Portican gives you access with an invitation; you can also create a store for a client straight from the portal.
5. The admin runs at admin.portican.com. Set the design under Shop › Look and feel: colours, fonts, corner radius, the Basic or Expert template and, for Expert, its style.
6. Build pages from blocks under Content › Website pages. Which blocks exist and which fields they have is covered in Blocks and fields.
7. Save a finished website as a file under Content › Website preset and use it as the starting point for your next client. The file format is described in Website preset.

What the platform allows and what it does not

• One store for everyone. Every client runs on the same build of the store. There is no custom template or code for a single client; you change the design and structure of a website through settings: the theme, the template, blocks and presets.
• No custom JavaScript in templates or blocks. A block carries text, links and options, and the store outputs them as text, never as HTML. A link that is not a safe URL is dropped by the platform.
• Tracking tags only through the measurement settings. They are connected under Marketing › Measurement and advertising, and only for the networks listed below. The store runs them according to the visitor's consent: before consent, Google receives only a cookieless signal (Consent Mode, advanced), and every other network starts only after consent to analytics or marketing.
• Google Tag Manager handles consent on its own. The container receives the consent state before it starts. Every tag inside it must have consent checks enabled (analytics_storage, ad_storage), otherwise it bypasses the consent banner; the platform cannot enforce that for you.
• Custom CSS only on top of hooks. With the Custom CSS Engine you write styles under Shop › Custom CSS. Every rule must start with a hook listed in Markup hooks, images come only from the store's media library and custom fonts are not supported yet. Before anything goes live, the server cleans the styles and tells you the line and the reason for each finding; every save is a version with a preview. Custom styles never apply to the checkout, sign-in, the customer account, legal pages or forms with personal data.
• Checkout, sign-in and the customer account have no hooks. Where customers type a password or pay, the platform's own design applies.
• The platform does not write legal texts. Terms and conditions, the privacy policy and the returns policy each have their place in the store; the merchant adds the wording with their own lawyer.

Measurement networks the store can connect

• Google Tag Manager analytics
• Google Analytics 4 analytics
• Microsoft Clarity analytics
• Google Ads marketing
• Meta (Facebook, Instagram) marketing
• ChatGPT ads marketing
• TikTok marketing
• Pinterest marketing
• LinkedIn marketing
• Microsoft Advertising marketing
• Sklik (Seznam) marketing
• Ecomail (newsletter) marketing

From the platform code. This list is built directly from the platform source code, and every deployment checks that the two still match.

How to report a bug

Email info@portican.com. We can fix a bug faster when your message includes:

• the address of the page where the bug appears,
• when it happened, with the date, time and time zone,
• what you expected and what happened instead,
• a screenshot, the browser and the device,
• for a hook, its value; for a preset, the file you used.

A hook from the list that is missing from a page, or sits somewhere other than its description says, is a platform bug. Please report it.