Using PhantomJSCloud Proxy

PriceFetchWP supports PhantomJSCloud as an optional proxy and browser-rendering provider.

PhantomJSCloud can be useful when an external website cannot be fetched reliably through a normal Direct Fetch, or when the page requires browser-style rendering before the price becomes available.

This guide explains how to connect PhantomJSCloud to PriceFetchWP, assign it to a URL Entry, and configure the available options.

– What Is PhantomJSCloud?

PhantomJSCloud is a third-party browser rendering service.

Instead of PriceFetchWP connecting directly from your WordPress instance to the external website, the request is sent through PhantomJSCloud:

Your WordPress Instance
        ↓
PhantomJSCloud
        ↓
External Website

PhantomJSCloud loads the external page using its own browser infrastructure and returns the resulting page content to PriceFetchWP.

This can help with websites that:

• block normal server-based requests
• require JavaScript rendering
• behave differently when fetched directly from a hosting server
• need more browser-like page loading before the price can be detected

PhantomJSCloud is optional. If a website works correctly using Direct Fetch, there is generally no need to use a proxy for that URL Entry.

– Getting a PhantomJSCloud API Key

To use PhantomJSCloud with PriceFetchWP, you will first need a PhantomJSCloud account and API key.

Create or sign in to your PhantomJSCloud account and locate your API key.

Once you have the key, return to:

PriceFetchWP → Settings → Proxy Integration

Select the PhantomJSCloud tab.

– Connect PhantomJSCloud to PriceFetchWP

Enter your PhantomJSCloud API key into the API key field.

Click: Verify

PriceFetchWP will make a test request to confirm that the API key can be used.

If verification is successful, click: Quick Save

Your API key and PhantomJSCloud settings will now be stored in PriceFetchWP.

Tip: Quick Save saves the Proxy Integration settings without requiring the entire settings page to refresh.

– Assign PhantomJSCloud to a URL Entry

Connecting an API key does not automatically send every PriceFetchWP request through PhantomJSCloud.

Proxy providers are selected per URL Entry.

Find the URL Entry you want to use with PhantomJSCloud and open: Advanced Options

Enable the proxy option and select: PhantomJSCloud

Save your settings.

PriceFetchWP will now use PhantomJSCloud when fetching prices for that URL Entry. A Proxy: PhantomJSCloud indicator will now show on this entry.

This allows you to continue using Direct Fetch for websites that do not need a proxy while only using PhantomJSCloud where necessary.

– Cost / Performance Options

PriceFetchWP includes options that can reduce unnecessary page loading when PhantomJSCloud is used.

The recommended defaults are:

• Finish at DOM Ready
• Ignore images

These options can usually remain enabled unless a particular website requires different behavior.

– Finish at DOM Ready

Finish at DOM Ready (recommended) tells PhantomJSCloud that the page can be returned once the browser reaches the DOM Ready stage instead of waiting for every page resource to finish loading.

This can reduce the amount of time and resources required to fetch a page.

For price fetching, this is often sufficient because PriceFetchWP generally needs the page structure and price content rather than every image, advertisement, font, or other secondary resource.

When should I disable DOM Ready?

Some websites load or modify their price later in the page-loading process.

If:

• PhantomJSCloud successfully fetches the page
• your selector appears correct
• but the expected price is still missing

you can try disabling Finish at DOM Ready and run Test Entry again.

Disabling it allows PhantomJSCloud more time to finish loading page resources and JavaScript activity.

This does not guarantee that every dynamically generated price will become available, but it can help with websites where pricing appears later in the page-loading process.

– Ignore Images

Ignore images (recommended) tells PhantomJSCloud that image resources are not needed for the fetch.

PriceFetchWP normally does not need product images in order to retrieve a price.

Ignoring images can reduce unnecessary page loading and resource usage while still allowing PriceFetchWP to inspect the page content.

When should I disable Ignore Images?

For most price-fetching situations, this option should remain enabled.

However, unusual websites may depend on image-related page loading or scripts in ways that affect other page content.

If a site behaves differently through PhantomJSCloud and other troubleshooting steps have not helped, you can temporarily disable Ignore images and test the URL again.

For most websites, leaving this option enabled is recommended.

– Testing a URL with PhantomJSCloud

After assigning PhantomJSCloud to a URL Entry, use: Test Entry

The Test Entry results will show the fetch mode used for the request.

You should see PhantomJSCloud listed as the provider when the proxy is being used.

Review the result for:

• fetch status
• returned page
• selector matches
• regular price
• sale price
• any reported errors
• raw HTML

If the PhantomJSCloud fetch succeeds but the selector does not find a price, the problem may be related to the selector or the way the external website generates its pricing rather than the proxy connection itself.

– Direct Fetch Works — Should I Still Use PhantomJSCloud?

Usually, no.

If PriceFetchWP can reliably retrieve the correct price using Direct Fetch, continuing to use Direct Fetch is normally the simpler option.

A proxy provider is most useful when a particular website requires it.

Using proxy providers only where needed can also help reduce third-party usage.

⚠️ Common Issues

API key does not verify

Check that:

• the API key was copied correctly
• there are no extra spaces
• your PhantomJSCloud account is active
• your account has sufficient access or usage available

Then try Verify again.

PhantomJSCloud works but PriceFetchWP cannot find the price

A successful proxy request only confirms that the external page was fetched.

You should still verify:

• the XPath, ID, Class, or Script selector
• whether the expected price exists in the returned page
• whether the price is generated later by JavaScript
• whether Finish at DOM Ready should be disabled for that website

Use Test Entry to help determine where the failure occurs.

Direct Fetch fails but PhantomJSCloud works

This can happen when the external website treats server-based requests differently or requires browser-style rendering.

If PhantomJSCloud consistently retrieves the expected price, you can leave that provider assigned to the URL Entry.

The price appears in my browser but not PhantomJSCloud

Some websites depend on additional browser state or behavior such as:

• cookies
• sessions
• delayed JavaScript
• user interaction
• location
• personalized content

A browser-rendered fetch does not guarantee that every website will return exactly the same page or price that you see during a normal browser session.

– PhantomJSCloud Usage

PhantomJSCloud is a third-party service and has its own account limits, usage policies, and pricing.

PriceFetchWP does not control PhantomJSCloud billing or account usage.

For current usage and account information, refer to your PhantomJSCloud account and official PhantomJSCloud documentation.