Traffic exchange sites

How does it work?

• You enter the target html elements to be clicked in the page, either
  • By entering the text content of an tag
  • By entering the js/css selector of the element
• Automated browser of our exchanger software:
  • Scrolls to the element if it is outside of the viewport.
  • Determines center coordinates of the element after scrolling.
  • Send a real mouse click event (with isTrusted: true, not a programmatic click by javascript command) to that coordinate.
• Clicking is not limited to the first loaded page. You can simulate a real surfing user behaviour by defining a series of click actions with delays as follows
  • Wait 5 seconds to site get loaded and click ‘Accept All’ button to dismiss the cookie consent popup.
  • Wait 1 second and click to a product category to go to category page
  • Wait 5 seconds and click to a product link.
  • Wait 10 seconds and click to reviews tab
  • Wait 3 seconds and click load more reviews
  • Wait 10 seconds and click on another product link from the similar products section
• Consider your site’s load speed and use appropriate delays if necessary.

How to get the JS/CSS selector for an element?

• Open your website in Google Chrome.
• Right click on the element and click Inspect. This will open developer console of Google Chrome.
• You will see that the HTML code of the element you inspected is highlighted.
• Right click to the code > Copy > Selector.
• Paste it into the actions input box.
• See screenshots below.

How to test your actions performing well?

• You can use our exchanger software to test how your actions are processed by our automated traffic exchange software.
• Go to websites and get a test key by clicking  button under your website.
• Download and install traffic exchange software.
• Paste your test key and start exchanger.
• Clicking start button will fetch your website from the server and will show you how traffic exchanging users will be visiting your site.
• Visiting website stops after one visit. You can make changes in your actions, save them on website, and click start to test again.
• If you are using different actions for different device types and test for each device type, please save your website to use that device.

Important notes and limitations

Selector determined by google chrome is not always the most accurate selector. You can always contact us and ask for help from our support team to get the best selector.

Since we send a native click event on the screen (not a programmatic fake click with javascript), your element should be visible to be able to clicked. Such elements are not clickable:

Elements that are hidden by display: none or visibility: hidden css properties.

Elements that are outside the scrollable area, for example using negative margins/paddings values, transform or similar CSS tricks.

Elements behind other elements with absolute positioning and lower z-index. This is usually a case if your site is displaying a cookie consent modal overlay.

Elements that are inserted to DOM dynamically only when user scrolls down the page. (also content coming from infinite scrolling)

Links having custom target attribute such as target=”_blank” or similar will not open because the embedded browser in our exchanger software blocks all popups and windows due to security reasons.

Any link/element inside an iframe is not clickable. Most 3rd party Advertisement providers displays ads in your website inside an iframe and clicking an element inside those iframes is not possible. You can try to click the div in your own dom that you placed the ad code snippet, but it is not ethical and we do not recommend to do it.

Prefer Click By JS/CSS selector method over Click By Text because:

Text matching is prone to errors. Case mismatch or markup inside the text might prevent matching.

There might be multiple links with the same text within the page (for example a visible desktop navbar and a hidden mobile/sticky navbar) and in this an non-clickable element can be selected by text matching.

If your page has dynamic content, make sure that your selector does not have a content specific id that will change in the future.