Budget: 95 USD Deadline: 2 days
Hello. I can create such a script that will go through all the pages at your link with the already set filters, extract the necessary parameters (price, number of trades/sales per month, and others), apply your selection formula, and record the results in a table (Excel/Google Sheets/CSV).
Please clarify what implementation you need:
1. as a script on a PC/server (you run it manually or on a schedule and receive a file/table),
2. as a Telegram bot (you send the link to the bot, the bot scans by itself and sends the results, it can keep a history/table)?
Also, please specify which parameters need to be collected and in what format the table should be.
- Projects -
- Rating -
- Rating 306
Budget: 100 USD Deadline: 3 days
I can do it, but considering that it is necessary to process many pages, 120+ requests (if based on the link), Steam may temporarily limit access or ban. To avoid this, there are two options: either work through a proxy or make many delays between requests. There is a possibility not to use standard page scraping; I can send what data can be obtained. If that doesn't work, I will do it the usual way by collecting data from the pages.
Budget: 100 USD Deadline: 3 days
Hello. I developed a Steam analytics system. I am implementing a script in Python that will collect data from all pages, filter skins according to your formula, and create a convenient table. I am ready to discuss the details.
Example of work: https://freelancehunt.com/showcase/work/steam-analytic-bot/1966219.html
Budget: 100 USD Deadline: 3 days
Hello.
I am ready to implement a Python script for parsing the Steam Market based on the provided links with already built-in search parameters.
The script will:
- go through all pages of the market;
- extract the necessary parameters (price, trading volume over a period, etc.);
- filter the data according to the specified formula;
- save the result in a table (CSV / Excel - to be specified).
Before starting, I suggest briefly documenting:
- the data source (JSON/HTML),
- the list of parameters,
- the filtering formula and the format of the result.
After that, I will implement a stable and understandable tool ready for use.
- Projects -
- Rating -
- Rating 475
Budget: 99 USD Deadline: 1 day
ready to help you out with this
have huge experience working in full stack
will send you previous work to make sure we match
Budget: 100 USD Deadline: 1 day
Good day! I am ready to complete this project and have extensive experience in developing various applications.
- Projects 8
- Rating 5.0
- Rating 2 403
Budget: 100 USD Deadline: 3 days
Good day, I will do it in a couple of days, please send the complete technical specification, we will discuss in more detail.
Alex Sorokopud
Winning proposal- Projects 25
- Rating 5.0
- Rating 2 215
Budget: 125 USD Deadline: 2 days
Hello, I am a Python developer with over 5 years of experience. As someone who has been playing CS for a long time and understands how the Steam market works, I would be interested in implementing this functionality. I have an understanding of how Steam and the market operate. I write parsers both on request and with automation through Selenium/Playwright. I would be happy to discuss the details and move on to collaboration! After development, I will provide documentation and will fix bugs as they arise!
Budget: 100 USD Deadline: 1 day
Hello, I am ready to take on your order. I will write a script in Python for parsing and filtering. I will also try to write instructions for usage and customization. The price is $50.
- Projects 9
- Rating 5.0
- Rating 813
Budget: 100 USD Deadline: 2 days
Good day, I have experience in creating parsers, contact me, I will do it quickly and efficiently.
Budget: 100 USD Deadline: 2 days
Hello!
I have reviewed the task and generally understand the logic and goal of the project.
I am ready to implement a parser that goes through all pages of the marketplace, collects the necessary parameters (price, sales volume, etc.), subsequently filters according to the specified formula, and saves the result in a table.
It is important to clarify the details regarding specific platforms and the list of parameters, as the data structure varies among different marketplaces — we will discuss and agree on this before starting work.
I am ready to propose an optimal technical solution and discuss all nuances in private messages.
Budget: 100 USD Deadline: 3 days
Hello. I have extensive experience in writing parsers in Python, particularly for the Steam Market. I understand the specifics of your task and the main difficulty of Steam's protection against frequent requests, rate limiting. Since Steam blocks IPs for aggressive parsing, I will implement a system of "smart delays" and handle error 429. The script will work stably, not raising suspicion in the system. If you are interested, I look forward to your response.
Budget: 100 USD Deadline: 1 day
Good day, I have experience in parsing. I am ready to do it in a couple of days and to familiarize myself with the details in advance.
Budget: 100 USD Deadline: 1 day
Hello!
I have experience in parsing markets, specifically I have developed scripts for data collection from many websites, including third-party platforms with bot protection. I will implement a script in Python using BeautifulSoup or Scrapy to collect information from the specified URL.
I will be able to extract parameters such as price and number of trades, and store them in a table. I will add filtering based on specified criteria for the convenience of analyzing the obtained data.
I am ready to discuss the details!
Budget: 100 USD Deadline: 4 days
Good day,
I have extensive experience in parsing and working with data, I can create such a script/application with a user-friendly interface for you if needed.
Message me privately, we will discuss the formula and the full functionality of the script!
Budget: 194 USD Deadline: 5 days
Hello, we have already created different parsers, so there is a fundamental script that needs to be adjusted for Steam. Therefore, we offer our services for this task. Write to us, we will be happy to discuss the details.
Budget: 100 USD Deadline: 2 days
Good day
I have previously made Steam parsers, it is essential to pass cookies taken from the browser to the script.
I have extensive experience.
In what format do we ultimately save the data?
Proposals concealed
Proposals are currently absent
Current freelance projects in the category Data Parsing
Set up automatic daily updates of product availability on our website on prom.ua. We have a supplier who sends a price list of products in Excel format to our email every day. The items on our website and in the supplier's price list are the same. The values in the "stock" column are either out of stock, a number, or more than a box - these need to be updated on the site to either Ready for shipment or Out of stock. Items that are not in the supplier's price list should remain unchanged. Please propose a solution, timeline, and budget. Thank you in advance for your response, I look forward to collaborating with a specialist.
Hello! I am looking for a performer for ongoing collaboration who is knowledgeable about Opencart. A person who is available and has a positive attitude) Parsing, uploading products in two languages UA + ru, as well as forming the necessary markup immediately I want to complete the work in several stages. 1. Update stock for all suppliers and completely remove outdated products from the site and database. 2. Refinement of the product category, specifically parsing subcategories. 3. Parse new items in old categories. 4. Parse new suppliers into new categories.
A project needs to be implemented for collecting and structuring a large array of images from open web sources (initially 2000 images). The task includes: - automated image collection; - uploading files in the highest available quality; - classifying images by categories. Expected results: - a structured image database; - a clear cataloging system; - delivery of the results via Google Drive or another agreed method;
Good day! Two tasks need to be completed: 1. Develop a product parser from an external website (10–40 thousand items, marketplace) with structured data saved in MySQL for subsequent output in WordPress. 2. Install and configure n8n on VPS, as well as organize AI content processing: prompt setup, text rewriting, image processing, SEO optimization, and text checking for AI detection. You can estimate the cost of completing both the entire project and each task separately. .
Task: one dashboard with all business metrics — advertising, funnel, payments, manager performance, revenue planning. Data is pulled automatically via API. Scope: only the YCL direction (employment in Europe). Kommo has other directions — only YCL funnel deals will be included in the repository (filter by funnel/tag to be agreed upon).1. Data Sources (Integrations) Kommo CRM — leads, deals, funnel stages, responsible persons, sources, dates of transitions between stages (must keep history), reasons for refusals, custom deal fields (see point 2). Stripe — payments, amounts, statuses (success/failure/refund), linked to deals. Meta Ads — expenses, impressions, clicks, CPL, leads by campaigns (currently operational). Google Ads, Reddit Ads, LinkedIn Ads — planned; architecture — extensible connectors without core rework. SEO/organic— Google Search Console + GA4. Cross-link: traffic source → lead in Kommo → payment in Stripe (UTM, deal ID in Stripe metadata — propose the mechanism). 2. Mandatory Cuts (Deal Fields in Kommo) Each metric must be filtered/grouped by: Client Citizenship (Kenya, Nigeria, India, etc.). Residence Status: lives in their country / expat (already in Europe). These are two different segments with different cycles, conversion rates, and checks. Country of Placement / Service: Poland, Serbia, Slovakia, Germany (ZAV). Manager, team, traffic channel, period. If any fields are missing in Kommo — the executor indicates which fields need to be added, the client adds them.3. Funnel and Leading Indicators Data by funnel, for each stage — summary and leading metrics: Traffic → lead: leads, CPL by channels + day-to-day expense/click dynamics. Lead → qualification: conversion + first response speed, touches/calls to the manager per day, unanswered leads. Qualification → contract/invoice: conversion + sent offers, stalled deals (days in stage above norm). Invoice → payment: payments, average check + unpaid invoices, failed payments. Summary: revenue, ROMI by channels, run rate to monthly plan. 4. Deal Cycle Average and median lead → payment cycle (business benchmark ~4 weeks), cycle trend over time. Breakdown of cycle by stages (how many days a deal sits at each stage) — to see which stage is dragging. List of deals that have stalled at a stage longer than normal. Cycle breakdown by segments: citizenship, residence status, country of placement, manager. 5. Early Warning of Decline (Key Block) Since the cycle is ~4 weeks, today's leads = payments in a month. The system must: Compare leads/qualifications of the current week with the moving average (4 weeks) and issue an alert if there is a downward deviation: “leads -X%, with a 4-week cycle expect a payment decline in the week [date].” Build payment forecast for 4 weeks ahead from the current pipeline: deals at each stage × historical conversion of the stage × remaining cycle. Highlight in red weeks where the forecast is below plan — with time to react. 6. Additional Payments and Sales Planning In the Kommo deal card, the date and amount of the planned additional payment are stored. The system must: Collect a calendar of upcoming additional payments: total expected, by weeks/months. Highlight overdue additional payments (date passed, no payments in Stripe) — a separate list for follow-up. Calculate the monthly plan as: plan − already paid − scheduled additional payments = how many new sales are needed (in money and in deal units at average check). Weekly schedule: additional payments + forecast of new payments against the weekly plan. 7. Manager Performance Daily snapshot for each manager: touches/calls, conversations, sent offers, payments — for each day separately, with a chart over the period. Progress on personal plan compared to monthly pace (ahead / on pace / behind). Benchmarking with colleagues. 8. Visualization and Roles “Traffic lights” (green/yellow/red) for key metrics relative to norms/plans; progress scales; trend graphs; mobile adaptive. Roles: CEO — everything; COO — entire funnel and managers; team lead — their team; manager — their metrics and position relative to colleagues. 9. Reports and AI Automated reports on schedule (daily summary, weekly report) in the dashboard and/or messenger. Free-form queries (“how has CPL from Meta changed over 2 weeks?”) — LLM over the repository. Alerts in the red zone and according to the rules from points 5–6. 10. Technical Expectations and Staging Repository (PostgreSQL/BigQuery or equivalent) + ETL: Kommo webhooks + periodic synchronization (15–60 min). Frontend: custom or BI tool — propose with justification; requirements for roles, traffic lights, forecasts, and AI queries must be implementable. Stages: (1) audit and metrics map → (2) MVP: Kommo + Stripe + Meta, funnel, traffic lights, roles → (3) deal cycle, early warning, additional payments and plan → (4) SEO, AI reports, alerts → (5) new advertising channels. Payment is staged, with a demo for each stage. In the response, indicate: similar projects (end-to-end analytics), stack with justification, timeline and cost estimates by stages, monthly ownership cost (hosting, tokens, licenses).