Safe Page Generator

Adspect comes with built-in safe page generator developed and maintained by our partners Comsign. These tools are designed to help you create safe pages quick and easy.

For technical support, please contact Comsign directly.

The generator can automatically integrate Adspect streams into generated pages for you:

  1. Create a stream and select “No action” for safe page action;
  2. In the Generator section (or on the Safe Page Generator tab of the stream’s Integration page, which is the same) select the stream to be integrated from the dropdown list and press “Generate”;
  3. Upload the generated ZIP archive to your hosting and unpack.

Safe Page Generator

Safe page generator is the most basic of all generators. It lets you control page content theme either by selecting from a pre-defined list of themes or by entering your own keywords in the same theme field. You may additionally choose language for automatic text translation.

Generated page content is randomized heavily and is proven to pass reviews on all major ad platforms, including Google Ads, Facebook, and TikTok Ads.

WordPress Generator

WordPress generator is functionally identical to the safe page generator and has the same controls, but generates pages based on WordPress CMS instead. The key concept of this generator is the fact that WordPress-based websites are overwhelmingly ubiquitous on Internet, thereby making its HTML code layout indistinguishable from layouts of hundreds of real websites. Technologically advanced corporations such as Google or Meta cannot tell WordPress safe pages from real WordPress websites even by using machine learning systems, which guarantees very high campaign approval rates.

This generator can produce both static HTML pages as well as complete WordPress instances with PHP source code and embedded SQLite database. In the latter case, the following system requirements apply:

Default WordPress administrator credentials are:

  • Username: user
  • Password: 12345

Google Play Generator

Google Play generator creates safe pages that are universally accepted by ad networks. Despite its name, it is suitable for any sort of ad campaigns, not just mobile apps. It produces fine-looking landing pages that promote apps from the Google Play Store.

It works as follows:

  1. Choose an app on Google Play Store that best fits your ad by keywords or creatives. The store is huge and offers apps for pretty much any theme or niche, so you are guaranteeed to find a fitting one.
  2. Specify the app’s page link in the generator interface (e.g. https://play.google.com/store/apps/details?id=com.whatsapp) and press the Generate button. After a moment you will be displayed a page preview. You may also specify an Adspect stream at this point–the generator will automatically integrate the stream for you using reverse PHP integration.
  3. Press the Download button to download the page as a ZIP archive. This archive contains the complete landing page suitable to be deployed on your server.

Landing pages from the Google Play generator promote apps that were previously approved by Google Play Store reviewers, so the content is guaranteed to be accepted by policy teams of any ad networks. The business model used by these pages is also transparent: promoting apps for profits.

App Store Generator

App Store generator works similarly to Google Play generator, but scrapes content from App Store instead.

Comsign API

Pro plan subscription gives you access to Comsign API for automated safe page generation.

Authentication

Comsign API employs HTTP Basic authentication scheme in which API key is supplied as username and password is left blank, i.e. every request to API must have a mandatory Authorization header that has the following format:

Authorization: Basic <authKey>

The <authKey> field in the Authorization header is formed by base64-encoding a string composed of the API key and a colon appended to it. You may find your API key in profile.

Example code in PHP:

<?php
$apiKey = 'SEbMw152aoe2ArffS7yjEJzJ_MFnd33e';
$authKey = base64_encode($apiKey . ':');

For convenience, there’s a readily encoded value of <authKey> available in your profile in the Authorization Header field.

Some HTTP clients offer native support for HTTP Basic authentication scheme which will set the Authorization header for you (e.g. Python Requests provides the requests.auth.HTTPBasicAuth class.) In this case pass your API key for username and leave password blank.

Generator Endpoint

To generate a safe page preview or ZIP archive you must send an HTTP GET request to the URL https://api.comsign.io/v2 and specify generation settings in URL parameters, e.g:

https://api.comsign.io/v2?product=wp&seed=12345&target=beauty&lang=en_US&sid=346fc84f-1cd6-47b8-b4fd-237ff55b4438&zip=true

Supported URL parameters:

  • product (required) – identifier of a tool that will be used to generate the safe page:
    • wp – WordPress generator;
    • sf – newsfeed generator;
    • gp – Google Play generator;
    • ap – App Store generator;
    • sc – page scraper;
  • target (required) – theme for WordPress and newsfeed generators, or target URL for Google Play and App Store generators and page scraper;
  • lang (required) – language code for automatic translation (see list of supported language codes below);
  • php=1 – for WordPress generator, makes it generate a PHP version instead of the default HTML version;
  • seed – any value that will be used to initialize the pseudo-random number generator; requests with the same value will produce the same safe page; if this parameter is omitted, then it will be picked randomly;
  • keywords – keywords that will be embedded into safe page code, separated by commas;
  • domain – domain name that will be specified on terms of service and privacy policy pages;
  • zip=true – selects to generate a ZIP archive instead of the default preview image;
  • sid – Adspect stream ID for automatic reverse PHP integration.

Language Codes

The following translation language codes are supported:

  • en_US – English
  • ru_RU – Russian
  • de_DE – German
  • fr_FR – French
  • it_IT – Italian
  • uk_UA – Ukrainian
  • es_ES – Spanish
  • vi_VN – Vietnamese
  • th_TH – Thai
  • sl_SL – Slovenian
  • sk_SK – Slovak
  • sr_RS – Serbian
  • ro_RO – Romanian
  • mn_MN – Mongolian
  • ms_MY – Malay
  • mk_MK – Macedonian
  • lt_LT – Lithuanian
  • lv_LV – Latvian
  • ko_KR – Korean
  • kk_KZ – Kazakh
  • ja_JP – Japanese
  • ga_IE – Irish
  • id_ID – Indonesian
  • is_IS – Icelandic
  • hu_HU – Hungarian
  • he_IL – Hebrew
  • el_GR – Greek
  • nl_NL – Dutch
  • hr_HR – Croatian
  • zh_CH – Chinese
  • be_BY – Belarusian
  • az_AZ – Azerbaijanian
  • hy_AM – Armenian
  • ka_GE – Georgian
  • cs_CZ – Czech
  • bg_BG – Bulgarian
  • ar_SA – Arabian
  • af_ZA – Afrikaans
  • pl_PL – Polish
  • sv_SE – Swedish
  • fi_FI – Finnish
  • pt_PT – Portuguese
  • tr_TR – Turkish
  • hi_IN – Hindi
  • et_EE – Estonian
  • da_DK – Danish
  • no_NO – Norwegian
  • bn_BD – Bengal